System and method for accessing information processor services from a mobile communication device

ABSTRACT

A system is for pushing information from a host system to a mobile data communication device upon sensing a triggering event. A redirector program operating at the host system enables a user to continuously redirect user-selected data items from the host system to the user&#39;s mobile data communication device upon detecting that one or more user-defined triggering events has occurred. The redirector program operates in connection with event generating applications and repackaging systems at the host system to configure and detect particular user-defined events, and to repackage the user-selected data items in an electronic wrapper prior to pushing the data items to the mobile device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a division of U.S. patent application Ser. No. 12/341,400, filedDec. 22, 2008, which is a continuation of U.S. patent application Ser.No. 10/480,979, filed on Dec. 15, 2003, now U.S. Pat. No. 7,487,204,which claims priority from International Patent Application No.PCT/CA02/00917, filed on Jun. 18, 2002, which claims priority from U.S.Provisional Patent Application No. 60/298983, filed on Jun. 18, 2001.This application is related to U.S. Pat. No. 6,438,585, filed on Jan.16, 2001, which is a continuation-in-part of U.S. Pat. No. 6,219,694,filed on May 29, 1998, and U.S. Pat. No. 6,779,019, filed on Apr. 10,2000. This application is also related to the following commonly-ownedUnited States patents, all of which are related to application Ser. No.09/087,623, U.S. Pat. No. 6,701,378, U.S. Pat. No. 6,463,464, U.S. Pat.No. 7,209,955, and U.S. Pat. No. 6,463,463, all of the aboveapplications hereby incorporated herein by reference.

BACKGROUND

1. Field of the Invention

The present invention is directed generally toward the field of mobilecommunications, and in particular to managing the processing of messageattachments and other information from a mobile data communicationdevice.

A further aspect of the invention provides a system and method forsending message attachments or other information from the mobile datacommunication device to one or more processing devices. Systems andmethods according to this aspect of the invention are particularlyuseful for mobile devices, such as pagers, PDAs, cellular telephones,etc., that have limited memory capacity and thus may have difficultyprocessing attachment files.

2. Description of the Related Art

Present systems and methods for replicating (or redirecting) informationfrom a host system to a user's mobile data communication device aretypically “synchronization” systems in which the user's data items arewarehoused (or stored) at the host system for an indefinite period oftime and then transmitted in bulk to the mobile device only in responseto a user request. In these types of systems and methods, whenreplication of the warehoused data items to the mobile device isdesired, the user typically places the mobile device in an interfacecradle that is electrically connected to the host system via some formof local, dedicated communication. Software executing on the mobiledevice then transmits commands via the local communications link to thehost system to cause the host to begin transmitting the user's dataitems for storage in a memory bank of the mobile device.

In these known synchronization schemes, the mobile unit “pulls” thewarehoused information from the host system in a batch each time theuser desires to replicate information between the two devices.Therefore, the two systems (host and mobile) only maintain the same dataitems after a user-initiated command sequence that causes the mobiledevice to download the data items from the host system. A generalproblem with these synchronization systems is that the only time thatthe user data items are replicated between the host system and themobile data communication device is when the user commands the mobiledevice to download or pull the user data from the host system. Fiveminutes later a new message could be sent to the user, but the userwould not receive that message until the next time the user fetches theuser data items. Thus, a user may fail to respond to an emergency updateor message because the user only periodically synchronizes the system,such as once per day. Other problems with these systems include: (1) theamount of data to be reconciled between the host and the mobile devicecan become large if the user does not “synchronize” on a daily or hourlybasis, leading to bandwidth difficulties, particularly when the mobiledevice is communicating via a wireless packet-switched network; and (2)reconciling large amounts of data, as can accrue in these batch-modesynchronization systems, can require a great deal of communicationbetween the host and the mobile device, thus leading to a more complex,costly and energy-inefficient system.

A more automated, continuous, efficient and reliable system of ensuringthat user data items are replicated at the user's mobile device istherefore needed.

There remains an additional need for such a system and method thatprovides flexibility in the types and quantities of user data items thatare pushed from the host system to the mobile data communication deviceand that also provides flexibility in the configuration and types ofevents that can serve to trigger the redirection of the user data items.

There remains yet an additional need for such a system and method thatcan operate locally on a user's desktop PC or at a distance via anetwork server.

There remains still another need for such a system and method thatprovides for secure, transparent delivery of the user-selected dataitems from the host system to the mobile device.

There remains an additional need for such a system and method in whichthe user is provided with a flexible means of processing messageattachments that may be too large or incompatible with the configurationof the mobile device.

SUMMARY

A system and method of pushing user-selected data items from a hostsystem to a user's mobile data communication device upon detecting theoccurrence of one or more user-defined event triggers is provided. Asused in this application, the term host system refers to the computerwhere the redirector software is operating. In one embodiment, the hostsystem is a user's desktop PC, although, alternatively, the host systemcould be a network server connected to the user's PC via a local-areanetwork (“LAN”), or could be any other system that is in communicationwith the user's desktop PC.

A redirector program operating at the host system enables the user toredirect or mirror certain user-selected data items (or parts of dataitems) from the host system to the user's mobile data communicationdevice upon detecting that one or more user-defined triggering eventshas occurred. In this application, the terms “information,” “dataitems,” “messages,” and “datagrams” are used interchangeably to mean aninformation object that is received at or sent from the host system orthe mobile device. Also operating at the host system are varioussub-systems that can be configured to create triggering events, such asa screen saver sub-system or a keyboard sub-system, as well assub-systems for repackaging the user's data items for transparentdelivery to the mobile data device, such as a TCP/IP sub-system or oneor more E-Mail sub-systems. Other sub-systems for creating triggeringevents and repackaging the user's data items could also be present atthe host system. The host system also includes a primary memory storewhere the user's data items are normally stored.

Using the redirector program, the user can select certain data items forredirection, such as E-mail messages, calendar events, meetingnotifications, address entries, journal entries, personal reminders etc.Having selected the data items for redirection, the user can thenconfigure one or more event triggers to be sensed by the redirectorprogram to initiate redirection of the user data items. Theseuser-defined trigger points (or event triggers) include external events,internal events and networked events. Examples of external eventsinclude: receiving a message from the user's mobile data communicationdevice to begin redirection; receiving a similar message from someexternal computer; sensing that the user is no longer in the vicinity ofthe host system; or any other event that is external to the host system.Internal events could be a calendar alarm, screen saver activation,keyboard timeout, programmable timer, or any other user-defined eventthat is internal to the host system. Networked events are user-definedmessages that are transmitted to the host system from another computercoupled to the host system via a network to initiate redirection. Theseare just some of the examples of the types of user-defined events thatcan trigger the redirector program to push data items from the host tothe mobile device. Although in a preferred embodiment it is anticipatedthat the configuration that specifies which data items will beredirected and in what form will be set at the host system, suchconfiguration may be set or modified through data sent from the mobilecommunications device.

In addition to the functionality noted above, the redirector programprovides a set of software-implemented control functions for determiningthe type of mobile data communication device and its address, forprogramming a preferred list of message types that are to be redirected,and for determining whether the mobile device can receive and processcertain types of message attachments, such as word processor or voiceattachments. The determination of whether a particular mobile device canreceive and process attachments is preferably initially configured bythe user of that mobile device at the host system. This configurationcan be altered on a global, per message basis or per device basis bytransmitting a command message from the mobile device to the hostsystem. If the redirector is configured so that the mobile data devicecannot receive and process word processor or voice attachments, then theredirector routes these attachments to an external machine that iscompatible with the particular attachment, such as an attached printeror networked fax machine or telephone. Other types of attachments couldbe redirected to other types of external machines in a similar fashion,depending upon the capabilities of the mobile device. For example, if auser is traveling and receives a message with an attachment that theuser's mobile device can process or display, the user may from a mobilecommunications device send a command message to the host systemindicating that that attachment is to be sent to a fax machine at ahotel where the user will be spending the evening. This enables the userto receive important E-mail attachments as long as the host system isprovided with sufficient information about the destination where theattachment is to be forwarded.

Once an event has triggered redirection of the user data items, the hostsystem then repackages these items in a manner that is transparent tothe mobile data communication device, so that information on the mobiledevice appears similar to information on the user's host system. Thepreferred repackaging method includes wrapping the user data items in anE-mail envelope that corresponds to the address of the mobile datacommunication device, although, alternatively, other repackaging methodscould be used, such as special-purpose TCP/IP wrapping techniques, orother methods of wrapping the user selected data items. The repackagingpreferably results in E-mail messages generated by the user from themobile device to be transmitted from the host system, thus enabling theuser to appear to have a single E-mail address, such that the recipientsof messages sent from the mobile communications device do not know wherethe user was physically located when the message was first sent. Therepackaging also permits both messages to the mobile device and sentfrom the mobile device to be encrypted and decrypted as well ascompressed and decompressed.

In an alternative system and method, the redirector program executes ona network server, and the server is programmed to detect numerousredirection event triggers over the network from multiple user desktopcomputers coupled to the server via a LAN. The server can receiveinternal event triggers from each of the user desktops via the network,and can also receive external event triggers, such as messages from theusers' mobile data communication devices. In response to receiving oneof these triggers, the server redirects the user's data items to theproper mobile data communication device. The user data items andaddressing information for a particular mobile device can be stored atthe server or at the user's PC. Using this alternative configuration,one redirector program can serve a plurality of users. This alternativeconfiguration could also include an Internet- or intranet-basedredirector program that could be accessible through a secure webpage orother user interface. The redirector program could be located on anInternet Service Provider's system and accessible only through theInternet.

In another alternative configuration, a redirector program operates atboth the host system and at the user's mobile data communication device.In this configuration, the user's mobile device operates similarly tothe host system described below, and is configured in a similar fashionto push certain user-selected data items from the mobile device to theuser's host system (or some other computer) upon detecting an eventtrigger at the mobile device. This configuration provides two-waypushing of information from the host to the mobile device and from themobile device to the host.

An advantage of this system and method is that triggering of continuousand real-time redirection of user-selected data items from a host systemto a mobile data communication device is provided. Other advantagesinclude: (1) flexibility in defining the types of user data to redirect,and in defining a preferred list of message types that are to beredirected or preferred senders whose messages are to be redirected; (2)flexibility in configuring the system to respond to numerous internal,external and networked triggering events; (3) transparent repackaging ofthe user data items in a variety of ways such that the mobile datacommunication device appears as though it were the host system; (4)integration with other host system components such as E-mail, TCP/IP,keyboard, screen saver, webpages and certain programs that can eithercreate user data items or be configured to provide trigger points; (5)the ability to operate locally on a user's desktop system or at adistance via a network server; (6) the ability to receive, process, andmanage attachment redirection; (7) the ability to dynamically change anddynamically re-route attachment redirection; and (8) management of dataitem attachments and other information processing from a mobilecommunication device.

A method of controlling an information processor using a mobilecommunication device is provided. The method may include the steps ofobtaining service information, including at least one service addressassociated with a service provided by the information processor, from aservice information provider, sending a communication signal from themobile communication device to the information processor using theservice address, receiving the communication signal at the informationprocessor, and performing an information processing operation inresponse to the communication signal.

A system for accessing services of an information processor with amobile communication device is also provided, and may comprise a serviceinformation provider located remotely from the information processor andthe mobile communication device, wherein the service informationprovider includes service information comprising one or more serviceaddresses associated with the information processor, and an interfacebetween the service information provider and the mobile communicationdevice for transferring the service information associated with theinformation processor to the mobile communication device. The mobilecommunication device obtains the service information associated with theinformation processor via the interface, and each service addressenables the mobile communication device to access a particular serviceof the information processor.

These are just a few of the many advantages of the systems and methodsdescribed in more detail below. As will be appreciated, each system andmethod is capable of other and different embodiments, and its severaldetails are capable of modifications in various respects. Accordingly,the drawings and description of preferred embodiments set forth beloware to be regarded as illustrative in nature and not restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system diagram showing the redirection of user data itemsfrom a user's desktop PC (host system) to the user's mobile datacommunication device, where the redirector software is operating at theuser's desktop PC.

FIG. 2 is a system diagram showing the redirection of user data itemsfrom a network server (host system) to the user's mobile datacommunication device, where the redirector software is operating at theserver.

FIG. 3 is a block diagram showing the interaction of the redirectorsoftware with other components of the host system in FIG. 1 (the user'sdesktop PC) to enable the pushing of information from the host system tothe user's mobile data communication device.

FIG. 4 is a flow chart showing the steps carried out by the redirectorsoftware operating at the host system.

FIG. 5 is a flow chart showing the steps carried out by the mobile datacommunication device to interface with the redirector software operatingat the host system.

FIG. 6 sets forth a system for redirecting messages having attachmentsbetween a host system and a mobile device.

FIG. 7 is a flow diagram setting forth a method of redirecting a messageattachment to an attachment displayer that is identified by the mobiledevice.

FIG. 8 is a flow diagram setting forth a method of redirecting a messageattachment to an attachment displayer that is identified by the hostsystem.

FIG. 9 is alternative system configuration of FIG. 6.

FIG. 10 is an illustrative block diagram of a preferred mobilecommunication device in which the systems and methods described hereinmay be implemented.

FIG. 11 is a block diagram of a system with an information processor andassociated service information providers.

FIG. 12 is a block diagram of an alternate information processor anddirectory arrangement.

FIG. 13 is a block diagram showing a system of information processors,networks and directories.

FIG. 14 illustrates several interfaces using which a unique identifierassociated with an information processor may be determined.

FIG. 15 shows the major functional components of a sample informationprocessor, a printer.

FIG. 16 is a system diagram illustrating a mobile device-controlledprint operation.

FIG. 17 is a system diagram illustrating a print by reference operation.

FIG. 18 is a system diagram similar to FIGS. 16 and 17, illustrating afurther print operation.

FIG. 19 shows a flow diagram of mobile device operations associated witha printing process incorporating multiple printing functions.

FIG. 20 shows an example menu relating to a print function.

DETAILED DESCRIPTION OF THE DRAWINGS

Referring now to the drawings, FIG. 1 is an example system diagramshowing the redirection of user data items (such as message A or C) froma user's office PC (host system) 10 to the user's mobile datacommunication device 24, where the redirector software (program) 12 isoperating at the user's PC. Message A in FIG. 1 represents an internalmessage sent from desktop 26 to the user's host system 10 via LAN 14.Message C in FIG. 1 represents an external message from a sender that isnot directly connected to LAN 14, such as the user's mobile datacommunication device 24, some other user's mobile device (not shown), orany user connected to the Internet 18. Message C also represents acommand message from the user's mobile data communication device 24 tothe host system 10. As described in more detail in FIG. 3, the hostsystem 10 preferably includes, along with the typical hardware andsoftware associated with a workstation or desktop computer, theredirector program 12, a TCP/IP subsystem 42, a primary message store40, an E-mail subsystem 44, a screen saver subsystem 48, and a keyboardsubsystem 46.

In FIG. 1, the host system 10 is the user's desktop system, typicallylocated in the user's office. The host system 10 is connected to a LAN14, which also connects to other computers 26, 28 that may be in theuser's office or elsewhere. The LAN 14, in turn, is connected to a widearea network (“WAN”) 18, preferably the Internet, which is defined bythe use of the Transmission Control Protocol/Internet Protocol(“TCP/IP”) to exchange information, but which, alternatively could beany other type of WAN. The connection of the LAN 14 to the WAN 18 is viahigh bandwidth link 16, typically a T1 or T3 connection. The WAN 18 inturn is connected to a variety of gateways 20, via connections 32. Agateway forms a connection or bridge between the WAN 18 and some othertype of network, such as an RF wireless network, cellular network,satellite network, or other synchronous or asynchronous land-lineconnection.

In the example of FIG. 1, a wireless gateway 20 is connected to theInternet for communicating via wireless link 22 to a plurality ofwireless mobile data communication devices 24. Also shown in FIG. 1 ismachine 30, which could be a FAX machine, a printer, a system fordisplaying images (such as video), a cellular phone, or a machinecapable of processing and playing audio files, such as a voice mailsystem. Machine 30 is also referred to herein as an attachmentdisplayer. This system also includes the ability to redirect certainmessage attachments to such an external machine 30 if the redirectorprogram configuration data reflects that the mobile device 24 cannotreceive and process the attachments, or if the user has specified thatcertain attachments are not to be forwarded to mobile device 24, even ifsuch device can process those attachments.

For example, consider an E-mail sent to a user that includes threeattachments—a word processing document, a video clip and an audio clip.The redirection program could be configured to send the text of theE-mail to the remote device, to send the word processing document to anetworked printer located near the user, to send the video clip to astore accessible through a secure connection through the Internet and tosend the audio clip to the user's voice mail system. This example is notintended to limit the breadth and scope of redirection, but rather toillustrate the variety of possibilities embodied in the redirectionconcept. The attachment redirection capabilities, as well as processingmanagement attachment or information processing are further describedbelow with reference to FIGS. 6-8.

The mobile data communication device 24 is preferably a hand-heldtwo-way wireless paging computer, a wirelessly enabled palm-topcomputer, a mobile telephone with data messaging capabilities, or awirelessly enabled laptop computer, but could, alternatively be othertypes of mobile data communication devices capable of sending andreceiving messages via a network connection 22. Although it ispreferable for the system to operate in a two-way communications mode,certain aspects of the system could be beneficially used in a “one andone-half” or acknowledgment paging environment, or even with a one-waypaging system. The mobile data communication device 24 includes softwareprogram instructions that work in conjunction with the redirectorprogram 12 to enable the seamless, transparent redirection ofuser-selected data items. FIG. 4 describes the basic method steps of theredirector program 12, and FIG. 5 describes the steps of thecorresponding program operating at the mobile device 24.

FIG. 10 is an illustrative block diagram of a preferred mobilecommunication device 24 in which the systems and methods describedherein may be implemented. The mobile communication device 24 ispreferably a two-way communication device having at least voice and datacommunication capabilities. The device preferably has the capability tocommunicate with other computer systems on the Internet. Depending onthe functionality provided by the device, the device may be referred toas a data messaging device, a two-way pager, a cellular telephone withdata messaging capabilities, a wireless Internet appliance or a datacommunication device (with or without telephony capabilities).

Where the device 24 is enabled for two-way communications, the devicewill incorporate a communication subsystem 911, including a receiver912, a transmitter 914, and associated components such as one or more,preferably embedded or internal, antenna elements 916 and 918, localoscillators (LOs) 913, and a processing module such as a digital signalprocessor (DSP) 920. As will be apparent to those skilled in the fieldof communications, the particular design of the communication subsystem911 will be dependent upon the communication network in which the deviceis intended to operate. For example, a device 24 destined for a NorthAmerican market may include a communication subsystem 911 designed tooperate within the Mobitex™ mobile communication system or DataTAC™mobile communication system, whereas a device 24 intended for use inEurope may incorporate a General Packet Radio Service (GPRS)communication subsystem 911.

Network access requirements will also vary depending upon the type ofnetwork 919. For example, in the Mobitex and DataTAC networks, mobiledevices such as 24 are registered on the network using a uniqueidentification number or associated with each device. In GPRS networkshowever, network access is associated with a subscriber or user of adevice 24. A GPRS device therefore requires a subscriber identity module(not shown), commonly referred to as a SIM card, in order to operate ona GPRS network. Without a SIM card, a GPRS device will not be fullyfunctional. Local or non-network communication functions (if any) may beoperable, but the device 24 will be unable to carry out any functionsinvolving communications over network 919. When required networkregistration or activation procedures have been completed, a device 24may send and receive communication signals over the network 919. Signalsreceived by the antenna 916 through a communication network 919 areinput to the receiver 912, which may perform such common receiverfunctions as signal amplification, frequency down conversion, filtering,channel selection and the like, and in the example system shown in FIG.10, analog to digital conversion. Analog to digital conversion of areceived signal allows more complex communication functions such asdemodulation and decoding to be performed in the DSP 920. In a similarmanner, signals to be transmitted are processed, including modulationand encoding for example, by the DSP 920 and input to the transmitter914 for digital to analog conversion, frequency up conversion,filtering, amplification and transmission over the communication network919 via the antenna 918.

The DSP 920 not only processes communication signals, but also providesfor receiver and transmitter control. For example, the gains applied tocommunication signals in the receiver 912 and transmitter 914 may beadaptively controlled through automatic gain control algorithmsimplemented in the DSP 920.

The device 24 preferably includes a microprocessor 938 which controlsthe overall operation of the device. Communication functions, includingat least data and voice communications, are performed through thecommunication subsystem 911. The microprocessor 938 also interacts withfurther device subsystems such as the display 922, flash memory 924,random access memory (RAM) 926, auxiliary input/output (I/O) subsystems928, serial port 930, keyboard 932, speaker 934, microphone 936, ashort-range communications subsystem 940 and any other device subsystemsgenerally designated as 942.

Some of the subsystems shown in FIG. 10 perform communication-relatedfunctions, whereas other subsystems may provide “resident” or on-devicefunctions. Notably, some subsystems, such as keyboard 932 and display922 for example, may be used for both communication-related functions,such as entering a text message for transmission over a communicationnetwork, and device-resident functions such as a calculator or tasklist.

Operating system software used by the microprocessor 938 is preferablystored in a persistent store such as flash memory 924, which may insteadbe a read only memory (ROM) or similar storage element (not shown).Those skilled in the art will appreciate that the operating system,specific device applications, or parts thereof, may be temporarilyloaded into a volatile store such as RAM 926. It is contemplated thatreceived communication signals may also be stored to RAM 926.

The microprocessor 938, in addition to its operating system functions,preferably enables execution of software applications on the device. Apredetermined set of applications which control basic device operations,including at least data and voice communication applications forexample, will normally be installed on the device 24 during manufacture.A preferred application that may be loaded onto the device may be apersonal information manager (PIM) application having the ability toorganize and manage data items relating to the device user such as, butnot limited to e-mail, calendar events, voice mails, appointments, andtask items. Naturally, one or more memory stores would be available onthe device to facilitate storage of PIM data items on the device. SuchPIM application would preferably have the ability to send and receivedata items, via the wireless network. In a preferred embodiment, the PIMdata items are seamlessly integrated, synchronized and updated, via thewireless network, with the device user's corresponding data items storedor associated with a host computer system thereby creating a mirroredhost computer on the mobile device with respect to the data items atleast. This would be especially advantageous in the case where the hostcomputer system is the mobile device user's office computer system.Further applications may also be loaded onto the device 24 through thenetwork 919, an auxiliary I/O subsystem 928, serial port 930,short-range communications subsystem 940 or any other suitable subsystem942, and installed by a user in the RAM 926 or preferably a non-volatilestore (not shown) for execution by the microprocessor 938. Suchflexibility in application installation increases the functionality ofthe device and may provide enhanced on-device functions,communication-related functions, or both. For example, securecommunication applications may enable electronic commerce functions andother such financial transactions to be performed using the device 24.

In a data communication mode, a received signal such as a text messageor web page download will be processed by the communication subsystem911 and input to the microprocessor 938, which will preferably furtherprocess the received signal for output to the display 922, oralternatively to an auxiliary I/O device 928. A user of device 24 mayalso compose data items such as email messages for example, using thekeyboard 932, which is preferably a complete alphanumeric keyboard ortelephone-type keypad, in conjunction with the display 922 and possiblyan auxiliary I/O device 928. Such composed items may then be transmittedover a communication network through the communication subsystem 911.

For voice communications, overall operation of the device 24 issubstantially similar, except that received signals would preferably beoutput to a speaker 934 and signals for transmission would be generatedby a microphone 936. Alternative voice or audio I/O subsystems such as avoice message recording subsystem may also be implemented on the device24. Although voice or audio signal output is preferably accomplishedprimarily through the speaker 934, the display 922 may also be used toprovide an indication of the identity of a calling party, the durationof a voice call, or other voice call related information for example.

The serial port 930 in FIG. 10 would normally be implemented in apersonal digital assistant (PDA)-type communication device for whichsynchronization with a user's desktop computer (not shown) may bedesirable, but is an optional device component. Such a port 930 wouldenable a user to set preferences through an external device or softwareapplication and would extend the capabilities of the device by providingfor information or software downloads to the device 24 other thanthrough a wireless communication network. The alternate download pathmay for example be used to load an encryption key onto the devicethrough a direct and thus reliable and trusted connection to therebyenable secure device communication.

A short-range communications subsystem 940 is a further optionalcomponent which may provide for communication between the device 924 anddifferent systems or devices, which need not necessarily be similardevices. For example, the subsystem 940 may include an infrared deviceand associated circuits and components or a Bluetooth™ communicationmodule to provide for communication with similarly-enabled systems anddevices. As described in further detail hereinbelow, such short-rangecommunications components may be particularly useful in controllingprocessing of messages, message attachments and like information.

In an alternative embodiment, not explicitly shown in the drawings, themobile device 24 also includes a redirector program. In this embodiment,user selected data items can be replicated from the host to the mobiledevice and vice versa. The configuration and operation of the mobiledevice 24 having a redirector program is similar to that describedherein with respect to FIGS. 1-9.

A user can configure the redirector program 12 to push certainuser-selected data items to the user's mobile data communication device24 when the redirector 12 detects that a particular user-defined eventtrigger (or trigger point) has taken place. When a secondaryuser-defined event trigger (or trigger point) occurs, which could be thesame as the initial event trigger or could be a different event, thesystem may subsequently stop redirection. User-selected data itemspreferably include E-mail messages, calendar events, meetingnotifications, address entries, journal entries, personal alerts,alarms, warnings, stock quotes, news bulletins, etc., but could,alternatively, include any other type of message that is transmitted tothe host system 10, or that the host system 10 acquires through the useof intelligent agents, such as data that is received after the hostsystem 10 initiates a search of a database, a website, a bulletin boardor other local or remote data store. In some instances, only a portionof the data item is transmitted to the mobile device 24 in order tominimize the amount of data transmitted via the wireless network 22. Inthese instances, the mobile device 24 can optionally send a commandmessage to the host system to receive more or all of the data item ifthe user desires to receive it.

User-defined event triggers that can be detected by the redirectorprogram 12 in the preferred embodiment include external events, internalevents and networked events. External events preferably include: (1)receiving a command message (such as message C) from the user's mobiledata communication device to begin redirection, or to execute some othercommand at the host, such as a command to enable the preferred listmode, or to add or subtract a particular sender from the preferred list;(2) receiving a similar message from some external computer; and (3)sensing that the user is no longer in the vicinity of the host system;although, alternatively, an external event can be any other detectableoccurrence that is external to the host system. Internal events could bea calendar alarm, screen saver activation, keyboard timeout,programmable timer, or any other user-defined event that is internal tothe host system. Networked events are user-defined messages that aretransmitted to the host system from another computer coupled to the hostsystem via a network to initiate redirection. These are just some of theevents that could be used to initiate replication of the user-selecteddata items from the host system 10 to the mobile device 24.

FIG. 1 shows an E-mail message A being communicated over LAN 14 fromcomputer 26 to the user's desktop system 10 (also shown in FIG. 1 is anexternal message C, which could be an E-mail message from an Internetuser, or could be a command message from the user's mobile device 24).Once the message A (or C) reaches the primary message store of the hostsystem 10, it can be detected and acted upon by the redirection software12. The redirection software 12 can use many methods of detecting newmessages. One preferred method of detecting new messages is usingMicrosoft's® Messaging API (MAPI), in which programs, such as theredirector program 12, register for notifications or ‘advise syncs’ whenchanges to a mailbox take place. Other methods of detecting new messagescould also be used.

Assuming that the redirector program 12 is activated, and has beenconfigured by the user (either through the sensing of an internal,network or external event) to replicate certain user data items(including messages of type A or C) to the mobile device 24, when themessage A is received at the host system 10, the redirector program 12detects its presence and prepares the message for redirection to themobile device 24. In preparing the message for redirection, theredirector program 12 could compress the original message A, couldcompress the message header, or could encrypt the entire message A tocreate a secure link to the mobile device 24.

Also programmed into the redirector 12 is the address of the user'smobile data communication device 24, the type of device, and whether thedevice 24 can accept certain types of attachments, such as wordprocessing or voice attachments. If the user's type of mobile devicecannot accept these types of attachments, then the redirector 12 can beprogrammed to route the attachments to a fax or voice number where theuser is located using an attached fax or voice machine 30 or other typeof attachment displayer.

The redirector may also be programmed with a preferred list mode that isconfigured by the user either at the host system 10, or remotely fromthe user's mobile data communication device by transmitting a commandmessage C. The preferred list contains a list of senders (other users)whose messages are to be redirected or a list of message characteristicsthat determine whether a message is to be redirected. If activated, thepreferred list mode causes the redirector program 12 to operate like afilter, only redirecting certain user data items based on whether thedata item was sent from a sender on the preferred list or has certainmessage characteristics that if present will trigger or suppressredirection of the message. In the example of FIG. 1, if desktop system26 was operated by a user on the preferred list of host system 10, andthe preferred list option was activated, then message A would beredirected. If, however, desktop 26 was operated by a user not on thehost system's preferred list, then message A would not be redirected,even if the user of the host system had configured the redirector topush messages of type A. The user of the host system 10 can configurethe preferred list directly from the desktop system, or, alternatively,the user can then send a command message (such as C) from the mobiledevice 24 to the desktop system 10 to activate the preferred list mode,or to add or delete certain senders or message characteristics from thepreferred list that was previously configured. It should be appreciatedthat a redirection program could combine message characteristics andpreferred sender lists to result in a more finely-tuned filter. Messagesmarked as low priority or that are simple return receipts or messageread receipts, for example, could always be suppressed from redirectionwhile messages from a particular sender would always be redirected.

After the redirector has determined that a particular message should beredirected, and it has prepared the message for redirection, theredirector software 12 then sends the message A to a secondary memorystore located in the mobile device 24, using whatever means arenecessary. In a preferred embodiment this method is to send the messageA back over the LAN 14, WAN 18, and through the wireless gateway 20 tothe mobile data communication device 24. In doing so, the redirectorpreferably repackages message A as an E-mail with an outer envelope Bthat contains the addressing information of the mobile device 24,although alternative repackaging techniques and protocols could be used,such as a TCP/IP repackaging and delivery method (most commonly used inthe alternative server configuration shown in FIG. 2). The wirelessgateway 20 requires this outer envelope information B in order to knowwhere to send the redirected message A. Once the message (A in B) isreceived by the mobile device 24, the outer envelope B is removed andthe original message A is placed in the secondary memory store withinthe mobile device 24. Repackaging and removing the outer envelope inthis manner causes the mobile computer 24 to appear to be at the samephysical location as the host system 10, thus creating a transparentsystem.

In the case where message C is representative of an external messagefrom a computer on the Internet 18 to the host system 10, and the host10 has been configured to redirect messages of type C, then in a similarmanner to message A, message C would be repackaged with an outerenvelope B and transmitted to the user's mobile device 24. In the casewhere message C is representative of a command message from the user'smobile device 24 to the host system 10, the command message C is notredirected, but is acted upon by the host system 10.

If the redirected user data item is an E-mail message, as describedabove, the user at the mobile device 24 sees the original subject,sender's address, destination address, carbon copy and blind carboncopy. When the user replies to this message, or when the user authors anew message, the software operating at the mobile device 24 adds asimilar outer envelope to the reply message (or the new message) tocause the message to be routed first to the user's host system 10, whichthen removes the outer envelope and redirects the message to the finaldestination, such as back to computer 26. The outgoing redirectedmessage from the user's host system 10 is preferably sent using theE-mail address of the host mailbox, rather than the address of themobile device, so that it appears to the recipient of the message thatthe message originated from the user's desktop system 10 rather than themobile data communication device. Any replies to the redirected messagewill then be sent to the desktop system 10, which if it is still inredirector mode, will repackage the reply and re-send it to the user'smobile data device, as described above.

FIG. 2 is an alternative system diagram showing the redirection of userdata items from a network server 11 to the user's mobile datacommunication device 24, where the redirector software 12 is operatingat the server 11. This configuration is particularly advantageous foruse with message servers such as Microsoft's® Exchange Server or LotusDomino™ Server, which is normally operated so that all user messages arekept in one central location or mailbox store on the server instead ofin a store within each user's desktop PC. This configuration has theadditional advantage of allowing a single system administrator toconfigure and keep track of all users having messages redirected. If thesystem includes encryption keys, these too can be kept at one place formanagement and update purposes.

In this alternative configuration, server 11 preferably maintains a userprofile for each user's desktop system 26, 28, including informationsuch as whether a particular user can have data items redirected, whichtypes of message and information to redirect, how to process varioustypes of message attachments, what events will trigger redirection, theaddress of the users' mobile data communication device 24, the type ofmobile device, and the user's preferred list, if any. The event triggersare preferably detected at the user's desktop system 26, 28 and can beany of the external, internal or network events listed above. Thedesktop systems 26, 28 preferably detect these events and then transmita message to the server computer 11 via LAN 14 to initiate redirection,or to subsequently halt redirection. Although the user data items arepreferably stored at the server computer 11 in this embodiment, theycould, alternatively, be stored at each user's desktop system 26, 28,which would then transmit them to the server computer 11 after an eventhas triggered redirection.

As shown in FIG. 2, desktop system 26 generates a message A that istransmitted to and stored at the host system 11, which is the networkserver operating the redirector program 12. The message A is for desktopsystem 28, but in this embodiment, user messages are stored at thenetwork server 11. When an event occurs at desktop system 28, an eventtrigger is generated and transmitted to the network server 11, whichthen determines who the trigger is from, whether that desktop hasredirection capabilities, and if so, the server (operating theredirector program) uses the stored configuration information toredirect message A to the mobile computer 24 associated with the user ofdesktop system 28.

As described above with reference to FIG. 1, message C could be either acommand message from a user's mobile data communication device 24, or itcould be a message from an external computer, such as a computerconnected to the Internet 18. If the message C is from an Internetcomputer to the user's desktop system 28, and the user has redirectioncapabilities, then the server 11 detects the message C, repackages itusing electronic envelope B, and redirects the repackaged message (C inB) to the user's mobile device 24. If the message C is a command messagefrom the user's mobile device 24, then the server 11 simply acts uponthe command message.

Turning now to FIG. 3, a block diagram showing the interaction of theredirector software 12 with additional components of the host system 10of FIG. 1 (the desktop PC) to enable more fully the pushing ofinformation from the host system 10 to the user's mobile datacommunication device 24 is set forth. These additional components areillustrative of the type of event-generating systems that can beconfigured and used with the redirector software 12, and of the type ofrepackaging systems that can be used to interface with the mobilecommunication device 24 to make it appear transparent to the user.

The desktop system 10 is connected to LAN 14, and can send and receivedata, messages, signals, event triggers, etc., to and from other systemsconnected to the LAN 14 and to external networks 18, 22, such as theInternet or a wireless data network, which are also coupled to the LAN14. In addition to the standard hardware, operating system, andapplication programs associated with a typical microcomputer orworkstation, the desktop system 10 includes the redirector program 12, aTCP/IP sub-system 42, an E-mail sub-system 44, a primary data storagedevice 40, a screen saver sub-system 48, and a keyboard sub-system 46.The TCP/IP and E-mail subsystems 42, 44 are examples of repackagingsystems that can be used to achieve the transparency of the system, andthe screen saver and keyboard sub-systems 46, 48 are examples of eventgenerating systems that can be configured to generate event messages orsignals that trigger redirection of the user selected data items.

The method steps carried out by the redirector program 12 are describedin more detail in FIG. 4. The basic functions of this program are: (1)configure and setup the user-defined event trigger points that willstart redirection; (2) configure the types of user data items forredirection and optionally configure a preferred list of senders whosemessages are to be redirected; (3) configure the type and capabilitiesof the user's mobile data communication device, including theconfiguration of attachment handling and type recognition; (4) receivemessages and signals from the repackaging systems and the eventgenerating systems; and (5) command and control the redirection of theuser-selected data items to the mobile data communication device via therepackaging systems. Other functions not specifically enumerated couldalso be integrated into this program.

The E-Mail sub-system 44 is the preferred link to repackaging theuser-selected data items for transmission to the mobile datacommunication device 24, and preferably uses industry standard mailprotocols, such as SMTP, POP, IMAP, MIME and RFC-822, to name but a few.The E-Mail sub-system 44 can receive messages A from external computerson the LAN 14, or can receive messages C from some external network suchas the Internet 18 or a wireless data communication network 22, andstores these messages in the primary data store 40. Assuming that theredirector 12 has been triggered to redirect messages of this type, theredirector detects the presence of any new messages and instructs theE-Mail system 44 to repackage the message by placing an outer wrapper Babout the original message A (or C), and by providing the addressinginformation of the mobile data communication device 24 on the outerwrapper B. As noted above, this outer wrapper B is removed by the mobiledevice 24, and the original message A (or C) is then recovered, thusmaking the mobile device 24 appear to be the desktop system 10.

In addition, the E-Mail sub-system 44 receives messages back from themobile device 24 having an outer wrapper with the addressing informationof the desktop system 10, and strips this information away so that themessage can be routed to the proper sender of the original message A (orC). The E-Mail sub-system also receives command messages C from themobile device 24 that are directed to the desktop system 10 to triggerredirection or to carry out some other function. The functionality ofthe E-Mail sub-system 44 is controlled by the redirector program 12.

The TCP/IP sub-system 42 is an alternative repackaging system. Itincludes all of the functionality of the E-Mail sub-system 44, butinstead of repackaging the user-selected data items as standard E-mailmessages, this system repackages the data items using special-purposeTCP/IP packaging techniques. This type of special-purpose sub-system isuseful in situations where security and improved speed are important tothe user. The provision of a special-purpose wrapper that can only beremoved by special software on the mobile device 24 provides the addedsecurity, and the bypassing of E-mail store and forward systems canimprove speed and real-time delivery.

As described previously, redirection can be triggered to begin (or end)upon detecting numerous external, internal and networked events, ortrigger points. Examples of external events include: receiving a commandmessage from the user's mobile data communication device 24 to beginredirection; receiving a similar message from some external computer;sensing that the user is no longer in the vicinity of the host system,such as by using the output of a digital camera, or by sensing theproximity of the user's mobile device using a wireless connection; orany other event that is external to the host system. Internal eventscould be a calendar alarm, screen saver activation, keyboard timeout,programmable timer, or any other user-defined event that is internal tothe host system. Networked events are user-defined messages that aretransmitted to the host system from another computer (not the mobiledevice) that is connected to the host system via a network to initiateredirection.

The screen saver and keyboard sub-systems 46, 48 are examples of systemsthat are capable of generating internal events. Functionally, theredirector program 12 provides the user with the ability to configurethe screen saver and keyboard systems so that under certain conditionsan event trigger will be generated that can be detected by theredirector 12 to start (or stop) the redirection process. For example,the screen saver system can be configured so that when the screen saveris activated, after, for example, 10 minutes of inactivity on thedesktop system, an event trigger is transmitted to the redirector 12,which starts redirecting the previously selected user data items. Whenthe screen saver becomes activated, for whatever reason, a second eventtrigger is generated in order to halt redirection. In a similar mannerthe keyboard sub-system can be configured to generate event triggerswhen no key has been depressed for a particular period of time, thusindicating that redirection should commence, and then to subsequentlygenerate another trigger when a key is depressed to stop redirection.These are just two examples of the numerous application programs andhardware systems internal to the host system 10 that can be used togenerate internal event triggers.

FIGS. 4 and 5, set forth, respectively, flow charts showing the stepscarried out by the redirector software 12 operating at the host system10, and the steps carried out by the mobile data communication device 24in order to interface with the host system. Turning first to FIG. 4, atstep 50, the redirector program 12 is started and initially configured.The initial configuration of the redirector 12 includes: (1) definingthe event triggers that the user has determined will triggerredirection; (2) selecting the user data items for redirection; (3)selecting the repackaging sub-system, either standard E-Mail, orspecial-purpose technique; (4) selecting the type of data communicationdevice, indicating whether and what type of attachments the device iscapable of receiving and processing, and inputting the address of themobile device; and (5) configuring the preferred list of user selectedsenders whose messages are to be redirected.

FIG. 4 sets forth the basic steps of the redirector program 12 assumingit is operating at a desktop system 10, such as shown in FIG. 1. If theredirector 12 is operating at a network server 11, as shown in FIG. 2,then additional configuration steps may be necessary to enableredirection for a particular desktop system 10, 26, 28 connected to theserver, including: (1) setting up a profile for the desktop systemindicating its address, events that will trigger redirection, and thedata items that are to be redirected upon detecting an event; (2)maintaining a storage area at the server for the data items; and (3)storing the type of data communication device to which the desktopsystem's data items are to be redirected, whether and what type ofattachments the device is capable of receiving and processing, and theaddress of the mobile device.

Once the redirector program is configured 50, the trigger points (orevent triggers) are enabled at step 52. The program 12 then waits 56 formessages and signals 54 to begin the redirection process. A messagecould be an E-Mail message or some other user data item than may havebeen selected for redirection, and a signal could be a trigger signal,or could be some other type of signal that has not been configured as anevent trigger. When a message or signal is detected, the programdetermines 58 whether it is one of the trigger events that has beenconfigured by the user to signal redirection. If so, then at step 60 atrigger flag is set, indicating that subsequently received user dataitems (in the form of messages) that have been selected for redirectionshould be pushed to the user's mobile data communication device 24.

If the message or signal 54 is not a trigger event, the program thendetermines at steps 62, 68 and 66 whether the message is, respectively,a system alarm 62, an E-Mail message 64, or some other type ofinformation that has been selected for redirection. If the message orsignal is none of these three items, then control returns to step 56,where the redirector waits for additional messages 54 to act upon. If,however the message is one of these three types of information, then theprogram 12 determines, at step 68, whether the trigger flag has beenset, indicating that the user wants these items redirected to the mobiledevice. If the trigger flag is set, then at step 70, the redirector 12causes the repackaging system (E-Mail or TCP/IP) to add the outerenvelope to the user data item, and at step 72 the repackaged data itemis then redirected to the user's mobile data communication device 24 viaLAN 14, WAN 18, wireless gateway 20 and wireless network 22. Controlthen returns to step 56 where the program waits for additional messagesand signals to act upon. Although not shown explicitly in FIG. 4, afterstep 68, the program could, if operating in the preferred list mode,determine whether the sender of a particular data item is on thepreferred list, and if not, then the program would skip over steps 70and 72 and proceed directly back to step 56. If the sender was on thepreferred list, then control would similarly pass to steps 70 and 72 forrepackaging and transmission of the message from the preferred listsender.

FIG. 5 sets forth the method steps carried out by the user's mobile datacommunication device 24 in order to interface to the redirector program12. At step 80 the mobile software is started and the mobile device 24is configured to operate with the system described above, including, forexample, storing the address of the user's desktop system 10.

At step 82, the mobile device waits for messages and signals 84 to begenerated or received. Assuming that the redirector software 12operating at the user's desktop system 10 is configured to redirect uponreceiving a message from the user's mobile device 24, at step 86 theuser can decide to generate a command message that will startredirection. If the user does so, then at step 88 the redirectionmessage is composed and sent to the desktop system 10 via the wirelessnetwork 22, through the wireless gateway 20, via the Internet 18 to theLAN 14, and is finally routed to the desktop machine 10. In thissituation where the mobile device 24 is sending a message directly tothe desktop system 10, no outer wrapper is added to the message (such asmessage C in FIGS. 1 and 2). In addition to the redirection signal, themobile device 24 could transmit any number of other commands to controlthe operation of the host system, and in particular the redirectorprogram 12.

For example, the mobile 24 could transmit a command to put the hostsystem into the preferred list mode, and then could transmit additionalcommands to add or subtract certain senders from the preferred list. Inthis manner, the mobile device 24 can dynamically limit the amount ofinformation being redirected to it by minimizing the number of senderson the preferred list. Other example commands include: (1) a message tochange the configuration of the host system to enable the mobile device24 to receive and process certain attachments; and (2) a message toinstruct the host system to redirect an entire data item to the mobiledevice in the situation where only a portion of a particular data itemhas been redirected.

Turning back to FIG. 5, if the user signal or message is not a directmessage to the desktop system 10 to begin redirection (or some othercommand), then control is passed to step 90, which determines if amessage has been received. If a message is received by the mobile, andit is a message from the user's desktop 10, as determined at step 92,then at step 94 a desktop redirection flag is set “on” for this message,and control passes to step 96 where the outer envelope is removed.Following step 96, or in the situation where the message is not from theuser's desktop, as determined at step 92, control passes to step 98,which displays the message for the user on the mobile device's display.The mobile unit 24 then returns to step 82 and waits for additionalmessages or signals.

If the mobile device 24 determines that a message has not been receivedat step 90, then control passes to step 100, where the mobile determineswhether there is a message to send. If not, then the mobile unit returnsto step 82 and waits for additional messages or signals. If there is atleast one message to send, then at step 102 the mobile determineswhether it is a reply message to a message that was received by themobile unit. If the message to send is a reply message, then at step108, the mobile determines whether the desktop redirection flag is onfor this message. If the redirection flag is not on, then at step 106the reply message is simply transmitted from the mobile device to thedestination address via the wireless network 22. If, however, theredirection flag is on, then at step 110 the reply message is repackagedwith the outer envelope having the addressing information of the user'sdesktop system 10, and the repackaged message is then transmitted to thedesktop system 10 at step 106. As described above, the redirectorprogram 12 executing at the desktop system then strips the outerenvelope and routes the reply message to the appropriate destinationaddress using the address of the desktop system as the “from” field, sothat to the recipient of the redirected message, it appears as though itoriginated from the user's desktop system rather than the mobile datacommunication device.

If, at step 102, the mobile determines that the message is not a replymessage, but an original message, then control passes to step 104, wherethe mobile determines if the user is using the redirector software 12 atthe desktop system 10, by checking the mobile unit's configuration. Ifthe user is not using the redirector software 12, then the message issimply transmitted to the destination address at step 106. If, however,the mobile determines that the user is using the redirector software 12at the desktop system 10, then control passes to step 110, where theouter envelope is added to the message. The repackaged original messageis then transmitted to the desktop system 10 at step 106, which, asdescribed previously, strips the outer envelope and routes the messageto the correct destination. Following transmission of the message atstep 106, control of the mobile returns to step 82 and waits foradditional messages or signals.

FIG. 6 sets forth a system for redirecting messages having attachments200, preferably using the redirector program discussed above. Thissystem preferably includes a desktop system 214A, which is associatedwith a mobile data communication device 214B, a host system 402, a relaysystem 410, and a plurality of attachment displayers 416. The hostsystem includes a datagram component 202A, a redirector program 202B,and an attachment processing component 202C. The datagram component 202Ais used to communicate datagrams 200 (i.e., messages or other types ofinformation) between the host system 202 and the desktop system 214A.The host system 202 could be similar to the server 11 shown above inFIG. 2, in which case the host 202 and the desktop 214A would be coupledvia a LAN. Alternatively, however, the host 202 could be remote from thedesktop 214A, and could be coupled to it via a LAN, WAN, the Internet208, a wireless network (not shown), a cableTV network, a satellitenetwork, or any other type of communication medium. The redirectorprogram 202B is similar to the redirector software described above. Theattachment processing component 202C provides the functionalitydescribed below with reference to FIGS. 7-8.

The host system 202 is separated from any external networks by afirewall system 206. Firewall systems 206 are known in this field, andprovide a security function for protecting an internal corporate networkfrom any external networks. The firewall 206 is, in turn, connected toan external network 208, such as the Internet, which is in turnconnected to a relay system 210 and then to the wireless network 212. Asnoted above, the wireless network 212 could be any type of digital oranalog wireless communication network, such as a packet data network, acellular network, a digital cellular network, a satellite network, amicrowave network, etc.

The mobile data communication device 214B is configured to operate onthe wireless network 212. In addition, the mobile data communicationdevice 214B is preferably configured to operate on one or moreshort-range wireless frequencies in order to wirelessly communicateinformation 215A, 215B between the mobile device 214B and the attachmentdisplayers 216. The mobile device 214B and the attachment displayers 216could be Bluetooth-enabled devices for communicating at the short-rangefrequencies associated with the Bluetooth wireless standard. Othershort-range wireless standards could also be utilized. The frequenciesat which the short-range communication link operate could be RF,microwave, cellular, optical, or Infrared frequencies. The attachmentdisplayers 216 are used by the mobile device 214B to process theattachment element 200B of the datagram 200, and may be one or more ofthe following devices: printers, fax machines, telephones, cellularphones, copying machines, video display, or any other type of devicecapable of processing an attachment.

In the system shown in FIG. 6, a datagram with an attached file 200 issent to the host system 202. The host system 202 then sends the datagramwith the attachment 200 intact to the desktop 204A of the recipient ofthe datagram 200 via the datagram component 202A. The datagram component202A recognizes the recipient address in the datagram 200 andsubsequently forwards the datagram 200 on to the desktop system 214A.The redirector component 202B of the host system 202B also sends thedatagram 200A, stripped of the attachment 200B, through the hostfirewall 206 to the relay 210 and then on to the mobile device 214B viathe Internet 208 and the wireless network 212. In a preferredembodiment, the attachment 200B is not initially redirected by the hostsystem 202 when the datagram 200A is redirected. Alternatively, it ispossible that automatic forwarding of attachments is possible;especially if the attachment is in a format that can be handled by themobile device. The datagram 200A contains the original message and alsocontains information about the attachment 200B, such as the file name,size, and file type.

In a preferred embodiment, after the datagram 200A (minus the attachment200B) is received at the mobile device 214B, the mobile device 214B willreceive a command either from the host system 202 or from the user ofthe mobile device to find an attachment displayer 216 within itsvicinity to process the attachment 200B. Alternatively, the mobiledevice 214B or user may automatically attempt to find an attachmentdisplayer when the datagram 200A is received. Preferably through shortrange wireless communication 215A, 215B, the mobile device 214B willquery 215A attachment displayers 216 in the local area of the mobiledevice 214B to determine whether they can process the attachment 200B.The attachment displayers 216 will then send back 215B to the mobiledevice 214B information pertaining to their location, electronicaddress, and the type of attachment files they can handle. The mobiledevice then processes this information regarding the attachmentdisplayers 216, and sends the host system 202 an attachment displayerchoice to use with the attachment 200B. The attachment component 202C ofthe host system receives the attachment displayer choice from the mobiledevice 214B, and will then send the attachment 200B to the chosenattachment displayer either through the wireless network 212, directlythrough the Internet 208, via a LAN connection, via a telephone orcellular connection, or via any other type of connection as specified bythe information provided from the chosen attachment displayer 216.

In an alternative embodiment of this system, the attachment component202C of the host system 202 would contain a database of attachmentdisplayers 216 to which it sends attachments 200B by default dependingon the file type. This database would include such information asdisplayer location, compatibility, and security. In this embodiment ofthe system, the mobile device does not chose the attachment displayer216 in real-time, although the user may configure the system in advanceto use a particular attachment displayer 216 contained in the database.Alternatively, the host system 202 may prompt the user of the mobiledevice 214B to select from a list of potential attachment displayers216, or the host may actively determine the location of the mobiledevice 214B, and then present a list of potential attachment displayers216 for selection by the user based upon positioning information of themobile device in relation to the potential attachment displayers 216.

FIG. 7 is a flow diagram setting forth a method of redirecting a messageattachment to an attachment displayer 216 that is identified by themobile device 214B. In step 220, the datagram with an attachment 200 isreceived by the host system 202. The redirector component 202B of thehost system 202 sends the datagram 200A to the mobile 214B withinformation about the attachment in step 222. Note that prior to thisstep, the attachment 200B is separated from the datagram 200, and is notdirectly transmitted to the mobile 214B along with the message portionof the datagram 200A. In step 224, the mobile device 214B is instructedto detect the availability of attachment displayers 216 in its localarea. This step could be accomplished automatically when the datagram200A is received, or it could be initiated through a menu selection bythe user of the mobile device 214B. Preferably, this step 224 is carriedout using a short-range wireless exchange 215A, 215B between the mobiledevice 214B and nearby attachment displayers 216.

Having obtained this information about the available attachmentdisplayers 216, the mobile device 214B in this step 224 then transmitsthe availability information to the host system 202. In step 226, thehost 202 determines whether the attachment 200B is a compatible formatfor at least one of the attachment displayers 216 that were discoveredin step 224. If a compatible attachment displayer is found, then thisdevice is selected for processing the attachment 200B. If a compatibledevice is not found, however, then in step 228 the attachment 200B isconverted into a suitable format by the host system 202 for one of thediscovered attachment displayers 216. In step 230, the attachmentdisplayer 216 selected by the host system 202 then sends the mobiledevice 214B its electronic routing address. This electronic address canbe an IP address, a telephone number, or a machine address. The mobiledevice 214B then sends the routing address of the attachment displayer216 back to the host system 202 in step 232. In step 234, the attachmentcomponent 202C of the host system 202 uses the routing address toredirect the converted attachment 200B to the selected attachmentdisplayer 216. The host system 202 then notifies the mobile device 214B,in step 236 that the attachment 200B has been redirected to theattachment displayer 216.

Alternatively to the method described in FIG. 7, instead of the hostsystem 202 selecting the appropriate attachment displayer 216, theselection could be made at the mobile device 214B. For example, knowingthe type of attachment at the mobile device 214B, which could beprovided in the datagram 200A, and having discovered the availableattachment displayers 216, the mobile device 214B could then select theappropriate attachment displayer 216, either automatically or based oninput from the user of the mobile device 214B. Electronic addressinformation of the selected attachment displayer 216 would then berouted to the host system 202, which would then transmit the attachment200B directly to the selected attachment displayer 216 by whatevernetwork connection is appropriate.

FIG. 8 is a flow diagram setting forth a method of redirecting a messageattachment to an attachment displayer 216, where the attachmentdisplayer 26 is identified by the host system 202. In step 240, the hostsystem 202 receives a datagram 200 with an attachment. The redirectorcomponent 202B sends the datagram (minus the attachment) 200A to themobile 214B with information about the attachment in step 242. In step244, the host system 202 determines the attachment format type. From adatabase of attachment displayers 216 coupled to the attachmentcomponent 202C of the host system 202, the host system 202 will matchthe attachment format type with a suitable attachment displayer 216 instep 246. In step 250, the host 202 redirects the attachment 200B to theselected attachment displayer 216 based on the information in theattachment component database. In step 252, the host sends anotification to the mobile device 214B when the attachment has beenredirected and at which attachment displayer 216 the attachment will beavailable.

If the attachment is not compatible with any of the attachmentdisplayers 216 in the attachment component database in step 248, thenthe host 202 may query the mobile device 214B in step 254. In step 256the mobile device 214B interrogates attachment displayers 216 within themobile device's vicinity, preferably via a short-range wirelesscommunication exchange 215A, 215B. The mobile device 214B then displaysthe information that the responsive attachment displayers 216 sent backto the device 214B in step 258. This information can include routingaddress, compatibility and physical location. The user of the mobiledevice 214B may then make the selection of the attachment displayer 216in step 260. In step 262, the mobile device 214B then sends the hostsystem 202 the selection of the attachment displayer 216 including therouting information for the selected device 216.

Alternatively, the host system 202 may make the selection of theappropriate attachment displayer 216 using location information of themobile device 214B. This location information can be derived based uponcommunications between the mobile device 214B and the wireless network212, or it can be based upon a query of the mobile device 214B totransmit its location information to the host system 202, which may beobtainable by a variety of methods, such as an internal GPS receiver, atriangulation methodology with a plurality of base stations of thewireless network, etc. In any event, the host system 202 uses the mobiledevice's location information to select the most appropriate attachmentdisplayer 216 by first selecting the attachment displayers 216 in thedatabase of displayers that are capable of processing the transactionand then by comparing location information of the selected displayers216 with the location information of the mobile device 214B.

An alternative embodiment to FIG. 6 is illustrated in FIG. 9. FIG. 9sets forth a system for redirecting messages having attachments 200,preferably using the redirector program discussed above. This systempreferably includes an attachment processing component 202C thatprovides the additional functionality described below. The attachmentprocessing component 202C converts attachments 200B into one or moreformats that are acceptable for the mobile device 214B, prior totransmission to the mobile device 214B, such that the mobile device 214Bcan display the attachment 202B to the user thereby not requiring theuse of attachment displayers 216. In this manner, the attachmentdisplayers may be circumvented. However, in this case the wirelessnetwork 212 preferably is robust and has a large bandwidth toaccommodate large attachment transmissions.

In one embodiment of the attachment processing component 202C,attachments are “trimmed” in that only a portion of the attachment 200Bis sent to the mobile device 214B. If the user after viewing theattachment desires to see the rest of the attachment, then the user maysend a command to push the remaining portion of the attachment to themobile device 214B. Alternatively, the user may request the attachmentto be sent to an attachment displayer 216. When the attachmentprocessing component 202C converts the attachments, the convertedattachment is preferably compressed in size and may be encrypted. Thepackaging of the attachments, if needed, is accomplished as discussedabove. Advantageously, the processing and overhead associated withconversions from a plurality of attachment formats to one or more commonformats compatible with the mobile device 214B is accomplished at thehost system 202.

Redirection of message attachments between a host system, a mobile datacommunication device and one or more attachment displayers has beendescribed in detail above. These general concepts may be furtherextended to the processing of not only message attachments but alsoother information, as described in further detail below. Therefore, inthe following description, the more general term “information processor”is used in reference to any device that may process an attachment, fileor other information. Although an attachment displayer is an example ofan information processor, it will be appreciated that according to theembodiments described below, an information processor may also processtypes of information other than message attachments.

In accordance with an embodiment of the present invention, eachinformation processor is registered or listed in a preferably publiclyaccessible directory. FIG. 11 is a block diagram of a system with aninformation processor and associated service information providers. Thesystem shown in FIG. 11 includes a printer 1102 as the informationprocessor, service information providers in the form of a servicesdirectory 1106 and a Universal Description, Discovery and Integration(UDDI) service cloud 1108, all connected to a WAN, shown as the Internet1104. Although FIG. 11 shows a printer 1102 as the informationprocessor, those skilled in the art will appreciate that similararrangements may be implemented for any other attachment displayers,such as fax machines, telephones, cellular phones, copying machines,video displays, or any other type of device capable of processing anattachment. Similarly, depending upon the preferences of an owner oroperator of the printer 1102, the printer 1102 and directory 1106 mayinstead be connected to a LAN instead of WAN 1104. For example, if theprinter 1102 is owned by a company and is intended for use only by itsemployees through the company's LAN, then the printer 1102 and directory1106 may be connected to the LAN instead of the Internet 1104. However,where the owner or operator of printer 1102 wishes to make printingservices publicly available, then such an arrangement as shown in FIG.11, with the printer 1102 and directory 1106 connected to a WAN such asthe Internet 1104 may be preferred.

An information processor such as the printer 1102 may be associated withone or more service information providers. The directory 1106 and UDDIservice cloud 1108 are examples of systems from which serviceinformation (i.e., any information required to access a service,determine the type of service, determine the location or type of theinformation processor that provides the service, etc.) may be obtained.Although two service information providers are shown in FIG. 11, aninformation processor may be associated with only one, or alternativelymore than two, service information providers. Operations involving eachof the service information providers 1106 and 1108 are described infurther detail below.

With reference first to the directory 1106, the printer 1102 and anyother information processor (not shown), like the attachment displayersdescribed above in conjunction with FIGS. 6-8, may have respectiveunique identifiers, as shown at 1110 or routing addresses. In a furtherembodiment, each service or capability of each information processor mayalso have a unique address. The directory 1106 then associates specificinformation processor addresses with corresponding service addresses, ifany, for that information processor, and may also associateinter-related information processors that may have some predeterminedlocation, logical or service affiliation. For example, a printer, faxmachine and a display or projector within a boardroom may be linkedwithin the directory 1106. Similarly, a directory record for a black andwhite printer might also include a reference or link to a directoryrecord for a physically proximate printer with colour or otherwiseenhanced printing capabilities. Information processors or services couldalso be grouped by type of service to provide for service typesearching. The operation and contents of the directory 1106 will bedescribed in further detail below.

An information processor or service address may be of one or moreaddress types, each address type suited for supporting differentinteraction modes, for example. An address type may be selected based oninformation processor owner or operator preference, the types of mobiledevices that an information processor is intended to support, the typeof transactions that an information processor is designed to handle, orpossibly further alternative or additional criteria. It is alsocontemplated that each information processor may have more than one typeof associated address, for example to support multiple device ortransaction types.

Information processors or services using an IP addressing scheme,including the current version 4 (IPv4) or future versions such asversion 6 (IPv6) may be best suited for implementing a software programinterface such as an application programming interface (API) forinteracting with the information processor or service, whereas a relatedUniversal Resource Locator (URL) addressing scheme may be better suitedfor Hypertext Transfer Protocol (HTTP) or Secure HTTP (HTTPS) basedinteractions. E-mail addressing, on the other hand, may be used forasynchronous interactions such as in an information push technique. Forexample, the printer 1102 and its associated services such as black andwhite printing and colour printing may appear in the directory 1106 asfollows:

-   -   For an IPv4 addressing scheme:        -   129.10.10.19 for main printer;        -   129.10.10.20 for black and white printing service on the            main printer; and        -   129.10.10.21 for colour printing on the main printer.    -   For a URL addressing scheme:        -   xxx://public_printer.corp.com as a main printer address            (where “xxx” is “http”);        -   xxx://public_printer.corp.com/bw for black and white            printing (where “xxx” is “http”); and        -   xxx://public_printer.corp.com/colour for colour printing            (where “xxx” is “http”).    -   In an E-mail addressing scheme:        -   public_printer@corp.com as a main printer SMTP address;        -   public_printer.bw@corp.com for black and white printing; and        -   public_printer.colour@corp.com for colour printing.

As described briefly above, more than one addressing scheme may be usedin the directory 1106, and a user wishing to access one or more of theservices of an information processor may then select the one of theaddresses in a format best suited to a desired type of processingtransaction.

The information processor and services directory 1106 may be indexed bya unique identifier. Each identifier may correspond to a particularregistered information processor, although each service may also beindexed with a different identifier. The directory 1106 preferablyprovides at least an association between a unique identifier and aninformation processor. Where information processor services areseparately indexed, an information processor record in the directory1106 preferably refers to or is otherwise linked with the records of theservices it provides. Each device and service may support configurableprocessing options, which may also be indexed by unique identifiers inthe directory 1106. If the unique identifier is not the address of theinformation processor, where access to the services of the informationprocessor is to be restricted for example, the directory should alsoprovide device and/or service addresses. A further function of addresstranslation might be provided by the directory 1106 in order to provideequivalent addresses, such as IP addresses, URL addresses and E-mailaddresses, for different interaction modes.

In general, any service information required in order to access aparticular information processor or its services could be provided in aninformation processor and service directory 1106. As such, otherfunctions or operations associated with a directory 1106 will beapparent to those skilled in the art and are therefore considered to bewithin the scope of the present invention. When the service directory1106 is indexed by unique identifiers, then service information mayinclude the service address, as well as other service- or informationprocessor-related information.

Turning now to the UDDI-based service information provider, the UDDIservice cloud 1108, UDDI is one of the most common solutions for thediscovery and integration of new services. UDDI provides a browser andAPI-centric view of dealing with dynamic services. The browser methodtreats potential service users as always online The API method alsoassumes always online and continuous high speeds for program to programcommunication. The UDDI method of host service registration is describedby the following documents, which may be found on the www.uddi.orgInternet web site: Version 2.0 Programmer's API Specification, Version2.0 Data Structure Specification, Version 2.0 Replication SpecificationVersion 2.0 Operator's Specification, Executive White Paper (version1.0), Technical White Paper (version 1.0), Using WSDL in a UDDI Registry1.05, Using WSCL in a UDDI Registry (1.02) and Providing a Taxonomy forUse in UDDI Version 2.

As those skilled in the art will appreciate, a UDDI service cloud suchas 1108 is normally distributed throughout the Internet 1104, but isshown connected to the Internet 1104 in FIG. 11 in order to avoidcongestion in the drawing. In UDDI, a user is able to make user ofso-called marketplace web sites and search portals, normally alsoconnected to the Internet 1104, to find required services. The UDDIservice cloud 1108 acts as a worldwide repository of service informationthat is accessible in a distributed manner through the Internet 1104.Behind the service cloud 1108 are actually databases or directories1114, 1116, perhaps using LDAP services or some other fast look-uptechnology to satisfy service requests. These databases 1114, 1116 mightbe distributed around the globe and may communicate using a UDDIpropagation technique as defined in the UDDI specification. Populatingthese databases 1114, 1116 are service providers that register serviceinformation associated with their information processors and/or servicesin the large service registry system.

UDDI and other similar types of service registry definitions all definea central store where all services can be found if desired. The UDDIspecifications describe ways to manipulate, change and replicate thisinformation between databases in the UDDI cloud 1108. Additionally, theservices may categorized into taxonomies, to further help with locatingand identifying the service needed. Taxonomies provide forclassification and identification of registered services.

When a company, person or organization decides that they want to createa public or semi-public service that should be made available to a wideaudience of users, the service creator or service provider propagatesthe service information to the UDDI service cloud 1108, one of itsunderlying databases or directories 1114, 1116, or possibly a newdatabase or directory. In FIG. 11, this is accomplished through the UDDIAPI 1112 in the printer 1102. The UDDI API 1112 may be configured toautomatically publish service information for the printer 1102 or itsservices to a new or existing database or directory in the UDDI servicecloud 1108. Once the service information has been published, a user of amobile communication device (not shown) may access the UDDI servicecloud 1108 to search for a particular type of service, to search forinformation processors in a particular location, or to browse serviceinformation for registered information processors and services to findan information processor or service supporting a processing operation tobe performed. Alternatively, the UDDI service cloud 1108 may be accessedusing a unique identifier 1110 of an information processor or service toobtain service information for a particular information processor orservice associated with the unique identifier.

The UDDI API 1112 may be developed and installed by a manufacturer orowner of an information processor such as the printer 1102. In addition,the API 1112 may be available separately from an information processor,and each time it is purchased and installed by an owner or operator ofan information processor, a new service registry entry is created in theUDDI service cloud 1108. Existing information processors could therebybe enabled for discovery via UDDI whenever its services are to be madeavailable.

Within the UDDI cloud 1108, further propagation of service informationmay take place so that the service information is distributed throughoutthe entire system of databases or directories 1114, 1116. Essentially,the act of publishing the service information once allows for a “publishonce access anywhere” design approach. This publishing can be doneprogrammatically or through manual processes through the UDDI APIdefinitions. Part of UDDI is a rich set of XML and SOAP-based commandsthat allow service providers to securely establish, modify and deleteentries in UDDI databases.

A UDDI implementation may also provide a list of new services forpotential service users. Service users are typically web browser users,but could also be software applications or programs looking forservices. A service user would typically start up a web browser tosearch for service information and perform searches until theinformation is found. This model is based on a request/response model,or a pull architecture. However, it is also possible that services maybe advertised by “pushing” service information to users. Such serviceadvertising is not restricted only to UDDI-based systems, but may alsobe implemented in directory-based systems as well.

As described briefly above, an information processor or its services maybe associated with more than one type of service information provider.For a private network, in which access to information processors andservices are restricted to network users, a private directory such as1106 may be most suitable. When an information processor is to beaccessible to a larger or more distributed group of users, a UDDI-basedsystem may be more feasible. In some circumstances, such as when onlycertain services are to be publicly accessible, whereas others are to beavailable only to a specific group of users, then public services couldbe registered in a UDDI service cloud and private services could belisted in a directory.

FIG. 12 is a block diagram of an alternate information processor anddirectory arrangement. This drawing illustrates the application of theunique address concept to a fax machine, a further example of aninformation processor. The fax machine 1202 is shown with not only thetraditional phone number, which is effectively an address in a publicswitched telephone network (PSTN) 1208, but also a network address on anetwork such as the Internet 1204. As described above, the network 1204may be a LAN or other WAN instead of the Internet 1204.

The fax machine 1202 preferably has a unique associated identifier bywhich related information such as one or more device addresses, serviceaddresses or links to records for associated services are indexed in thedirectory 1206. With the additional IP, URL and E-mail addressing asdescribed above, the fax machine 1202 is effectively converted into anintelligent device capable of providing its capabilities on the Internetor another network, such as an Internet based “print-to-fax” device,while retaining its more traditional PSTN-based facsimile functions.

FIG. 12 shows a unique identifier and directory-based system. It shouldbe apparent from FIG. 11 and the description above that the fax machine1202 and/or its services could also or instead be registered with, andassociated service information could be obtained from, a UDDI servicecloud, as indicated by the dashed lines enclosing the unique identifiersin the fax machine 1202.

FIGS. 11 and 12 each show an example of a single information processorand directory. However, the invention is in no way limited to sucharrangements. FIG. 13 is a block diagram showing a system of informationprocessors, networks and directories. The system of FIG. 13 includes aplurality of information processors 1302, 1306, 1307, 1310 and 1312, aLAN 1304 with an associated information processor and service directory1303 and security firewall 1305, a computer or network 1308 with itsinformation processor and service directory 1309, a wide area network1314 such as the Internet, with one or more information processor andservice directories 1317 and 1318, and a PSTN 1320.

Each information processor 1302, 1306, 1307, 1310 and 1312 in FIG. 13may be any device or system capable of processing files or otherinformation. Some information processors such as 1310 may be connectedto the WAN 1314, while others such as 1302, 1306 and 1307 communicatewith the WAN 1314 through further systems 1304 and 1308. One or more ofthe information processors, as shown at 1312, may also have interfacesto and addresses on additional networks such as the PSTN 1320. Althoughthe system diagram of FIG. 13 is more general than those shown in FIGS.11 and 12, those skilled in the art will appreciate that still otherarrangements of information processors, networks and directories maywell be associated with the same WAN 1314. Also, any of the informationprocessors or services supported by the information processors may alsoor instead be registered with a UDDI service cloud, as described above.Thus, FIG. 13 is intended for illustrative purposes only; the inventionis in no way limited thereto.

In FIG. 13, information processors such as 1310 and their associatedservices are registered in an information processor and servicedirectory 1317 on the WAN 1314. Information processors such as 1312 maysimilarly be registered in WAN directory 1317, even though suchprocessors, like the fax machine 1202 in FIG. 12, may have additionaladdresses on networks such as the PSTN 1320. For each registeredinformation processor and possibly each service provided thereby, thedirectory 1317 may store such information and provide such functionalityas described above, including for example associating a uniqueidentifier with an information processor or service, any associatedconfigurable processing options and one or more addresses of theassociated information processor or service, and providing alternateequivalent addresses, such as IP addresses, URL addresses and E-mailaddresses, for different interaction modes for an information processoror service.

Other information processors such as 1302, 1306 and 1307 may beconfigured for operation on a LAN 1304 or in conjunction with a computeror network 1308. The computer 1308 may for example be a server computeror an ISP system providing a gateway for subscriber systems (not shown)to access the Internet 1314. Each of the systems 1304 and 1308 may haveits own local information processor and service directory 1303 and 1309in which information processors connected thereto and their associatedservices are registered. Such local directories would preferably beaccessible by users authorized to access the systems 1304 and 1309. Asdescribed briefly above for example, where LAN 1304 is a corporatenetwork, located behind a security firewall 1305, the informationprocessor 1302 and directory 1303 may only be accessible by corporatenetwork users. Alternatively, the corporate network informationprocessor 1302 or the directory 1303 itself might also be registered inthe directory 1317 if local services are to be offered outside thenetwork 1304. Any access to such a restricted information processor 1302or information in the directory 1303 could then be controlled at thefirewall 1305.

Similar access arrangements could be implemented at the system 1308. Theinformation processors 1306 and 1307 would preferably be registered in alocal directory 1309 as well as the WAN directory 1317 if the servicesof the information processors 1306 and 1307 are to be provided to usersthrough the WAN 1314.

Each of the networks shown in FIG. 13 may further include additionaldirectories, such as shown at 1318. For example, directories may bespecific to particular services or types of devices. In the system ofFIG. 13, directory 1317 may be a printer or print service directorywhich stores information for all printers or other informationprocessors supporting print services that are connected to or accessiblethrough the WAN 1317. The directory 1318 may similarly be a fax machineand service directory. Other specific multiple-directory arrangementswill also be apparent to those skilled in the art.

Although system topologies may vary, the general operations of thedirectories and information processors will be substantially the same.An information processor or service may first be selected, for exampleby a user of a mobile communication device or a host system associatedwith the mobile device as described above. In one embodiment of theinvention, a mobile device user selects an information processor at hisor her current location. A directory may in some cases then be queried,with a unique identifier of the selected information processor orservice, for example. The service directory returns specific informationrequested or all information for the information processor or service.Service information may also or instead be available from a UDDIregistry or service cloud. As described above, UDDI may support servicetype searching, identifier-based access, browsing and selection ofprocessors or services, or possible other types of access and service orprocessor selection.

In a directory-based system, if an information processor having a uniqueidentifier is selected, then its unique identifier, which as describedabove may or may not be its associated routing address, must then bedetermined. FIG. 14 illustrates several interfaces using which a uniqueidentifier associated with an information processor may be determined.As shown in the Figure, an information processor 1402 may incorporate aninfrared module, shown as an Infrared Data Association (IrDA) compatibleinterface 1404, an RF module such as a Bluetooth module 1406 or an802.11 module 1407, a bar code 1408 or a text label 1410. The uniqueidentifier associated with the information processor 1402, as well asany identifiers associated with the services of the processor 1402 canthen be determined and input to a similarly-enabled mobile communicationdevice 1412-1418 as described in further detail below. As will beapparent to those skilled in the art, “Bluetooth” and “802.11” refer tosets of specifications, available from the Institute of Electrical andElectronics Engineers, relating to wireless personal area networks andwireless LANs, respectively.

It should be noted that the interfaces shown in FIG. 14 are not mutuallyexclusive. An information processor 1402 may incorporate more than oneof the interfaces 1404, 1406, 1407, 1408 and 1410 in order to providealternative identifier determination processes. Similarly, a singlemobile device may have more than one corresponding interface, such thata user may have a choice as to how an information processor or serviceidentifier is to be determined and input to the device.

Each of the different types of interfaces in FIG. 14 provides adifferent mechanism for communicating with a mobile device. Three ofthese are active (powered) interfaces that can be triggered to transmitthe unique identifier to a mobile device, whereas the others arepassive, relying on certain capabilities of the mobile device to capturethe unique identifier of the information processor 1402.

The active interfaces shown in FIG. 14 are based on an IrDA port 1404, aBluetooth communication module 1406, and an 802.11 module 1407. Whenqueried by a similarly enabled mobile communication device 1412, 1414,1415, these interfaces preferably transmit at least the uniqueidentifier associated with the information processor 1402, and possiblyadditional identifiers corresponding to each service supported by theinformation processor 1402, back to the mobile device. As shown in FIG.10 and described above, a mobile device may include one or moreshort-range communication subsystems 940 which would provide for suchcommunication between the mobile device and an information processor1402. An additional benefit of active interfaces such as 1404, 1406 and1407 is that they can not only transmit the unique identifier to themobile device, but may also be used to exchange further information witha mobile device, as described in detail below. However, they aredependent on their power source to be operational.

The passive interfaces shown in FIG. 14 include one or more encodedbarcodes 1408 and text labels 1410. A barcode scanner, implemented in amobile device as an auxiliary I/O subsystem 928 (FIG. 10) for example,may be used to automatically determine a unique identifier coded into abarcode label 1408. If an information processor 1402 and its servicesare separately registered in a directory, the processor 1402 may havemultiple barcode labels, any of which may be scanned depending upon theparticular service to be accessed. Text labelling (1410) of aninformation processor 1402 provides a further option for a mobile deviceuser to manually enter the appropriate identifier using a keyboard orother such user interface on a mobile device. When a barcode 1408 isprinted on a label attached to the device 1402, it will be apparent thatprocessor and/or service identifier text 1410 may be printed on the samelabel, provided that the text does not overlap or otherwise interferewith the barcode 1408. Passive interfaces such as 1408 and 1410 areinexpensive and do not need power source maintenance. However, theycannot exchange data with mobile devices.

Those skilled in the art will appreciate that other additional oralternative interfaces may also facilitate transfer of uniqueidentifiers from an information processor to a mobile device andpossibly exchange of further information between an informationprocessor and device. For example, coded surface acoustic wave (SAW)based communication subsystems such as those disclosed in co-pendingU.S. patent application Ser. No. 09/863,944, titled “WirelessCommunication System Using Surface Acoustic Wave (SAW) Second HarmonicTechniques”, filed on May 23, 2001, and U.S. patent application Ser. No.09/864,507, titled “Wireless Communication System Using Surface AcousticWave (SAW) Single-Phase Unidirectional Transducer (SPUDT) TypeTechniques”, filed on May 24, 2001, both incorporated in their entiretyherein by reference, are further contemplated passive interfaces.

A mobile communication device is thereby able to determine the uniqueidentifier associated with a particular information processor and/orservice. A query can then be prepared and sent to a directory in whichthe information processor or service has been registered. Likeinformation processor and service addresses, directories may also beaddressed according to one or more of the above schemes, depending upona preferred interaction mechanism. Directory addresses may for examplebe available from a central repository or provided by the informationprocessor through one of the interfaces 1404, 1406, 1407, 1408, 1410.The directory responds to such a query with any information required bythe device to use the selected information processor or service, asdescribed in further detail below. A mobile device may also obtainservice information from a UDDI service cloud or like system, asdescribed above.

Before proceeding with a detailed description of mobiledevice-controlled processing by an information processor, the functionalcomponents or modules of an example information processor will first bedescribed. FIG. 15 shows the major functional components of a sampleinformation processor, a printer. The printer in FIG. 15 is anillustrative example of an information processor, although it is to beunderstood that other information processors may include similarfunctional components.

As shown in FIG. 15, in accordance with an aspect of the invention aprinter may comprise, in addition to a substantially conventionalprinting apparatus designated 1502, an identifier module interface anddata processor 1504, a network interface 1506, and SMTP listener 1508,an E-mail processor and sequencer 1510, a print by reference processor1512, a document rendering and conversion engine 1514, a printer driver1516, a printer interface 1518 and a printer administration and jobcontrol module 1520.

The identifier module interface and data processor module 1504 wouldnormally be implemented only when the printer is enabled with an activeinterface to a mobile device, such as the IrDA port 1404 or Bluetoothmodule 1406 shown in FIG. 14. The interface and data processor module1504 manages communication to and from the active interfaces, includingfor example receipt of and responses to unique identifier queries frommobile devices and receipt of information to be printed from the mobiledevice, and also acts as an overall data and command processor. Forexample, in response to a print by reference command signal (describedbelow) received from a mobile device through an active interface, themodule 1504 would preferably invoke an operation by the print byreference processor to retrieve data referenced in the command signaland pass the data to the rendering and conversion engine. The interfaceand data processor module 1504 may also be configured to effectivelyadvertise device identifiers or services by transmitting signals from anactive interface. Such signals would serve to notify mobile devices inthe vicinity of the printer of the availability of the printer 1502 andits associated services. Since only active interfaces provide forexchange of information between an information processor and a mobiledevice, an identifier module and data processor need only be implementedif an information processor such as 1502 includes at least one activeinterface.

The network interface module 1506, as will be apparent to those skilledin the art, provides network connectivity for the information processorand preferably supports popular network protocols. In the example systemof FIG. 11, the printer 1102 preferably includes a network interfacethat supports such protocols as TCP/IP and HTTP, commonly used toexchange information on the Internet.

An SMTP listener 1508 provides a mechanism for receiving SMTP messages.Other message interfaces will be apparent to those skilled in the artand could be included in addition to or instead of the SMTP listener1508 to change or expand the messaging capabilities of an informationprocessor.

The E-mail processor and sequencer module 1510 preferably provides thefunctionality of opening SMTP and possibly other messages, decomposingthe message into individual components such as message text andattachments, and passing a sequenced data stream to downstreamprocessing components such as the rendering and conversion engine 1514.The E-mail processor and sequencer module 1510 also preferably createsadministration messages that may be packaged for example as SMTPmessages to be emailed back to a user with the result of a printrequest.

A print by reference processor 1512 provides for search and printfunctionality. The print by reference processor 1512 receives referencelocators provided in a print by reference command (described below) froma mobile device and uses them to retrieve information and pass suchinformation to downstream processing components such as the renderingand conversion engine 1514.

A rendering and conversion engine 1514 accepts data streams anddocuments and converts them to formats that can be rendered on theprinter 1502. Once information has been converted, the rendering andconversion engine 1514 uses the suitable printer driver 1516 to preparea data stream appropriate for the printer 1502. The printer driver 1516provides the software interface for services available on the physicalprinter 1502, whereas the printer interface 1518 provides the physicalinterface to the printer 1502.

The printer administration and job control module 1520 manages suchadministration and control activities as printer condition monitoring,print job queuing, printer or print job error recovery, print jobretries, printer and print job status monitoring and the like.

Of the modules shown in FIG. 15, the identifier module interface anddata processor 1504 (where at least one active interface is provided),the network interface 1506, the SMTP listener 1508 or similar messagingmodule and the E-mail processor and sequencer module 1510 would likelybe common to printers and other types of information processors. Theremaining modules as shown in FIG. 15 are printer-specific modules,although other information processors may include components and modulesthat perform similar functions.

Although not shown in FIG. 15, a UDDI API may also be provided if theprinter or any of its services are to be accessible via UDDI. Asdescribed above, UDDI-based information processor or service access maybe provided instead of or in addition to identifier and directory-basedprocessor or service access.

A print by reference processor 1512, as described above, embodies asearch and retrieve function. Thus, other information processors mayinclude a similar processor module to retrieve and display, E-mail, fax,transmit or perform other operations on information identified in acommand signal or alternatively to retrieve and execute a softwareapplication or automated script. Similarly, although the documentrendering and conversion engine 1514 in FIG. 15 converts a document to aprinter format, a rendering and conversion engine may be provided inother information processors to convert information into appropriatedisplay, transfer or processing formats. For example, receivedinformation intended for input to a particular system or softwareprogram associated with the information processor may be converted intoa suitable input format by a rendering and conversion engine. Althoughother types of information processor would not necessarily include aprinter driver 1516, a printer interface 1518 and a printeradministration and job control module 1520, the driver, interface andcontrol functionality would typically be provided by informationprocessor-specific modules.

The management of information processing operations on an informationprocessor will now be described in detail with reference to FIGS. 16-19.As above, the description relates to a printer as an illustrativeexample of an information processor, but the invention is in no waylimited thereto. In addition, although identifier and directory-basedoperations are described below, information processors and services mayalso or instead be discovered and accessed through UDDI.

FIG. 16 is a system diagram illustrating a mobile device-controlledprint operation. The system of FIG. 16 includes a mobile communicationdevice 1602, a wireless network 1604, a wireless gateway 1606, acorporate or other system 1608 with a security firewall 1609, a WAN suchas the Internet 1610, an information processor and services directory1612, a network interface and printer gateway 1614, a printer 1616, andinterfaces 1618, 1620, 1622 and 1624.

The mobile communication device 1602 is adapted to operate within thewireless communication network 1604. A wireless gateway 1606 providesfor communication from the wireless network 1604 to other networks suchas the WAN or Internet 1610 and possibly other networks such as 1608.The processor and services directory 1612 is preferably accessiblethrough the WAN or Internet 1610. The network interface and printergateway 1614 includes such components or modules as 1504 through 1520(FIG. 15) and provides for connection of the printer 1616 to theInternet 1610 and possibly communication between the printer 1616 andthe device 1602 where an active interface such as IrDA port 1618 or anRF module 1622 is implemented. The RF module may, for example, be aBluetooth module, and 802.11 module or other short-range RFcommunications interface. The interfaces 1618, 1620, 1622 and 1624operate substantially as described above to provide one or more uniqueidentifiers associated with the printer 1616 or its services to themobile communication device 1602. The active interfaces 1618 and 1622further provide for the exchange of information between the printer 1616and device 1602.

As described briefly above, service information associated with theinformation processor and/or any of its services may be stored in thedirectory 1612 and is preferably indexed according to a uniqueidentifier associated with the processor (printer 1616) or the servicessupported thereby. The device 1602 first determines the uniqueidentifier of the printer 1616 or a selected one of its services. If thedevice 1602 incorporates multiple interfaces, then the unique addressfor the selected printer 1616 or service may be captured using any ofsuch interfaces. The different identifier capture operationscorresponding to the four interfaces 1618 through 1624 are shown in FIG.16 at S1 a, S1 b, S1 c and S1 d.

In the operation at S1 a, the identifier is captured via the IrDA port1618 on the printer 1616 and a corresponding port (not shown) in thedevice 1602. The identifier may be transmitted to the device 1602 inresponse to a query (not shown) from the device 1602 to the printer 1616or transmitted from the printer 1616 as an advertising or notify signal.At S1 b the identifier is captured by scanning an appropriate barcode1620 with a scanner in the device 1602. S1 c indicates an identifiercapture operation using the RF printer interface 1622. A manualidentifier entry operation using a keyboard or other input interface onthe device 1602, with reference to text labelling 1624, is designated S1d. Depending on the particular interfaces implemented in the printer1616 and the device 1602, either of these operations S1 a-S1 d may beperformed to capture the identifier for the printer 1616 or anassociated service.

When the printer or service identifier has been captured by the mobiledevice 1602, a query (S2) may be sent to the directory 1612 for serviceinformation on the service or printer 1616. A routing address of thedirectory 1612, which may for example be an IP address, a URL or anE-mail address, may be known to the user of the device 1602 or stored onthe device 1602. Alternatively, the directory routing address may beavailable from a central directory address repository, or from someother source accessible by the mobile device 1602. The query istransmitted through the wireless network 1604, gateway 1606 and Internet1610 to the directory 1612.

The directory 1612 then responds (S3) to the query with serviceinformation relating to the selected printer 1616 or service. Theservice information may include an address, such as an IP address, URLor E-mail address, of the printer 1616 or the particular selectedservice, an indication of which if any print settings may be configuredin a print request, a default or preferred information exchangeprotocol, as well as any other information required by the device 1602in order to use the printer 1616 or its services. The device 1602 maythen store the service information provided by the directory into aninternal data store for later retrieval and use in subsequent printoperations. The directory 1612 may also provide information for anyrelated registered information processors and services, such as otherinformation processors in the vicinity of the printer 1616 or otherenhanced services offered by the printer 1616 or other processors in itsvicinity.

When the printer 1602 or its services have been registered in a UDDIsystem, a device 1602 may discover the printer 1602 or services bysearching or browsing databases or directories in a UDDI service cloudthrough the wireless network 1604, wireless gateway 1606 and Internet1610. Service information for an information processor or service maythen be obtained by the mobile device 1602 through the Internet 1610,wireless gateway 1606 and wireless network 1604.

The mobile device 1602 may also store the routing address and any otherinformation required to use a particular printer or service in aninternal data store. For example, the information associated with aprinter in a user's office or home may be stored in a device store anddesignated as a default information processor for print operations, andthe information for other printers may be stored on the device whenreceived. Instead of executing the initial printer identifier captureand directory query operations, a user may then simply select a printeror service from a list of those for which required information is storedon the device. A user interface such as a menu-driven interface may beprovided on the device to allow the user to select an operation, such asprint, and then a particular information processor, such as a printer,for which all required information is resident on the mobile device. Theuser may display a menu 2000 as depicted in FIG. 20 by providing aparticular input to the device using a device keyboard, keypad orauxiliary input element while information is being displayed on thedevice screen or a device screen cursor is located on an informationindicator or identifier (a file name, message title or the like) forexample.

The menu 2000 preferably includes operations relevant to the particulartype of information displayed or selected when the menu is invoked. Inthe menu 2000, the user may view, edit, save or print the selectedinformation. Further functions may also be supported, as indicated bythe “dots” in the menu 2000.

When the user selects “print” from the menu 2000, by highlighting“print” with a cursor as indicated by shading in the menu 2000 anddepressing a key or providing some other input on the device forexample, a further menu or list 2010 relating to the print function willpreferably be displayed. An example of a menu 2010 is depicted in FIG.20.

Print menu 2010 preferably lists all printers and services for which allrequired service information is available on the device, i.e. printer 1,printer 2 and service 1 in the above example, as well as a selection touse a new printer or service. The print menu 2010 may also provide achoice between transfer mechanisms and/or addressing schemes to be usedfor each configured printer or service. For a new printer or service,the user is preferably able to select an identifier capture mode, oralternatively a UDDI-based discovery operation. Such options for eachconfigured or new printer or service may instead be displayed in afurther menu upon selection of a particular printer or service orselection to configure a new printer or service. As those skilled in theart will appreciate, further and alternative menu choices may also beprovided. Example menus 2000 and 2010 are intended for illustrativepurposes only.

Thus, using such an interface, a user may select to print using aprinter for which service information is already stored on the deviceand thereby avoid the above initial operations associated with a printoperation. If the user selects to configure a new printer or service,the above identifier capture and possible directory query would thenproceed substantially as described above, or alternatively, a newprinter or service may be located and configured by obtaining serviceinformation.

Once the service information is available on a mobile device, the mobiledevice sends a communication signal to the information processor. Inresponse to the communication signal, the information processor performsan information processing operation. In the example of FIG. 16, dataresident on the mobile device 1602 is to be printed on the printer 1616.When both the printer 1616 and the mobile device 1602 include activeinterfaces, the communication signal, i.e. the information to beprinted, may be sent to the printer 1616 directly through an activeinterface, thereby avoiding the airtime costs and time delay associatedwith transmission of the information over the wireless network 1604. Asindicated at S4 a and S4 b respectively, the information may betransmitted via the IrDA port 1618 or the RF module 1622, in response toa menu selection as described above for, example. Path S4 c illustratesinformation exchange using an IP address or URL address for the printer1616, provided by the directory 1612. IP or URL address-basedinformation transfer may be necessary for example where the mobiledevice 1602 or the printer 1616 does not have an active interface, orwhere secure communications, using such a protocol as HTTPS, may bedesired.

As described above, the printer 1616 may also have an assigned E-mailaddress. The mobile device 1602 may then transmit the information to beprinted to the printer 1616 via an email path, designated as S4 d inFIG. 16. When the device 1602 is operating in conjunction withredirector software on a host system, the information to be printed mayfirst be sent to a desktop computer or a server computer 1608 throughthe wireless network 1604 and wireless gateway 1606. The information maythen be repackaged by the host system 1608 into an E-mail message orattached to an E-mail message and sent to the E-mail address of theprinter 1616. When the E-mail message is received at the printer 1616,the E-mail processor and sequencer module 1510 and the rendering andconversion engine 1512 (FIG. 15) perform any necessary conversionoperations and through an appropriate printer driver and printerinterface, print the information, as indicated at S5. This E-mailcommunication path may be preferred, for example, when asynchronousprocessing is acceptable or desired or where further processing of theinformation may be necessary.

Although the path S4 d between the mobile device 1602 and host system1608 is shown as bypassing the Internet 1610 and security firewall 1609,those skilled in the art will appreciate that such communications, likeany other external communications with the host system 1608, willactually be carried out through the firewall 1609, and unless thegateway is directly connected to the host system 1608, the path S4 dwill connect to the host system through the Internet 1610. However, itshould also be apparent from the description above that communicationsbetween a mobile device 1602 and a host system 1608 may be encrypted,which effectively extends the firewall 1609 to the mobile device 1602,such that the path S4 d may be considered to be behind the firewall1609, as shown, in the sense that communications on that path aresecure. If the information is of a sensitive or confidential nature,then the host system 1608 may encrypt the E-mail it sends to the printer1616, using Secure Multipurpose Internet Mail Extensions (S/MIME) orPretty Good Privacy™ (PGP™) for example. The E-mail processor module1510 (FIG. 15) would then decrypt the encrypted E-mail from the hostsystem to recover the information to be printed.

Provided that a mechanism for E-mail communication is available betweenthe mobile device 1602 and the printer 1616, then E-mail based printingof information from a mobile device 1602 will be possible. Such anE-mail transfer mechanism may be either indirect, through anintermediate system such as 1608, or more direct, between the mobiledevice 1602 and the printer 1616 through the wireless network 1604, somesort of gateway 1606 and the Internet 1610. E-mail transfers may also bein the clear or encrypted using PGP for example. However, theinformation processing management systems and methods of the presentinvention are in no way restricted to such secure communicationarrangements.

When the information to be printed is received by the printer 1616, theprinter may print not only the information, but also a separator orcover page, identifying for example an owner of the printed information,the number of pages printed and possibly other information related tothe print job or the content printed. Particularly where a printer orits services are used by many users, as is often the case with networkprinters, multiple print jobs may be in a printer output tray at anytime. Such a separator or cover page allows a user to more easilyidentify and retrieve a printout.

FIG. 17 is a system diagram illustrating a print by reference operation.In FIG. 17, the system components 1702, 1704, 1706, 1708, 1709, 1710,1712, 1714, 1716, 1708, 1720, 1722 and 1724 are substantially the samein structure and operation as the similarly labelled components in FIG.16. Although the overall structures of the systems in FIGS. 16 and 17are substantially the same, differences between the print operationsillustrated therein will become apparent from the following description.

A print by reference operation begins with a capture of the uniqueidentifier for the printer 1716 or a selected one of its services by themobile device 1702. As described above, depending upon the capabilitiesof the mobile device 1702 and the interfaces 1718, 1720, 1722 and 1724implemented in the printer, the mobile device 1702 may capture anidentifier via an IrDA port (S117 a), by scanning a bar code (S117 b),through an RF interface (S117 c) or by a user manually entering (S117 d)text label characters on a keyboard or other user interface of themobile device 1702. Using the unique identifier, a query may then besent (S217) to the directory 1712, which then responds (S317) with anyservice information required for the device 1702 to use the printer 1716or a service provided thereby. Service information may instead beobtained through a UDDI service cloud (not shown). These initialoperations are preferably substantially the same as those describedabove in conjunction with FIG. 16. If all required service informationfor the selected printer or service has been stored on the mobile device1702, then the user may access the stored service information, forexample through a series of menus as also described above, and therebyavoid the initial operations.

If the mobile device 1702 and printer 1716 are enabled with activeinterfaces, then a communication signal including a print by referencecommand or signal, including a reference locator for information to beprinted, may be exchanged directly with the printer 1716 through theIrDA port 1718 or RF module 1722, as indicated at S417 a and S417 b,respectively. A print by reference signal may instead be sent to an IPor URL address of the printer 1716, as indicated at S417 c. When E-mailcommunication or asynchronous processing is desired, then acommunication signal containing the reference locator for theinformation to be printed may be sent to a host system or service 1708,which may then encapsulate the reference locator into an E-mail messageor E-mail message attachment, possibly encrypt the E-mail, and forwardthe E-mail to the printer 1716 or service E-mail address (S417 c).

The reference locator for the information to be printed may be anaddress or other pointer. For example, the reference locator may be aURL that can be accessed by an Internet server (not shown) to providecontent, such as product marketing information and the like. Thereference locator may also invoke a search of an external informationsource, identifying for example the information source, a search engineto be used and search parameters to control the search.

The print by reference processor 1512 (FIG. 15) in the network interfaceand printer gateway 1714 uses the reference locator obtained from themobile device 1702 through an active interface or a printer or serviceIP, URL or E-mail address to request the information to be printed froman information source (S517). As described above, the information sourcemay be an Internet service (not shown) which uses the reference locatorto retrieve the information to be printed, by accessing a specifiedInternet location or performing a search for example. The information tobe printed, such as web page content or search results, is then returnedto the printer gateway 1714 (S617). Like the mobile device 1702 toprinter 1716 information transfers, the information retrieval operationbetween the printer gateway 1714 and an information source such as theInternet 1710 may be based on any common transfer mechanism, includingbut in no way limited to the above IP, URL or E-mail basedcommunications.

The rendering and conversion engine 1514 (FIG. 15) renders and convertsthe information returned by the Internet server or other informationsource. The information is then printed (S717) on the printer 1716through an appropriate printer driver 1516 and the printer interface1518 (FIG. 15). The printer may also print a cover or separator page toidentify the printout owner, the reference locator used to locate theinformation to be printed, and possibly other information related to theprint job.

Since the information to be printed may be in any of a plurality offormats, including various file types associated with different softwareapplication programs or commonly used Internet information formats suchas HTML, WML and XML, a plurality of rendering and conversion enginesare preferably provided in any information processor. Therefore, printer1716 may incorporate multiple rendering and conversion engines. Therendering and conversion capabilities of the printer 1716 are preferablyregistered in the directory 1712, possibly as different services, or aspart of service information. A user of a mobile device 1702 is then ableto determine whether or not the selected printer 1716 is able to processinformation of the type to be printed. If necessary, an alternateprinter or service may then be selected. For example, the user of device1702 may send a service type query to the directory 1712 in order tofind an information processor supporting the type of service required toperform a desired operation. UDDI-based systems may be especially insuch circumstances, when a mobile device must find or discover newinformation processors or services.

FIG. 18 is a system diagram similar to FIGS. 16 and 17, illustrating afurther print operation. The system components shown in FIG. 18 aresubstantially the same as similarly labelled components in FIGS. 16 and17.

The print operation illustrated in FIG. 18 involves printing of anE-mail message sent to the printer 1816 from the mobile device 1802.Such a print operation begins with a capture of the unique identifierfor the printer 1816 or a selected one of its services by the device1802, via an IrDA port (S118 a), by scanning a bar code (S118 b),through an RF interface (S118 c) or by a user manually entering (S118 d)text label characters into the mobile device 1802. A query may then besent (S218) to the directory 1812, which responds (S318) with anyservice information required for the device 1082 to use the printer 1816or one of its services. Alternatively, a printer or service may beselected from menu or list of printers and services for which allrequired service information is stored on the mobile device 1802. Theservice information need then only be retrieved from a store within themobile device 1802. Service information may also be available to themobile device 1802 from a UDDI system.

In the example of FIG. 18, the mobile device 1802 forwards acommunication signal, in the form of an E-mail message (S418), with orwithout attachments, to the E-mail address of the printer 1816 or aselected service. The E-mail message may be sent to the printer orservice address directly, or through a host or intermediate system 1808.As described above, the E-mail may be sent to the printer 1816 in theclear or encrypted. Encrypted E-mails would then be decrypted by theE-mail processor and sequencer module 1510 (FIG. 15) in the networkinterface and gateway component 1814.

Emails received by the SMTP listener 1508 (FIG. 15) in the networkinterface and printer gateway 1814 are forwarded to the E-mail processorand sequencer 1510, which will separate the E-mail into its differentcomponents, as described above, and create multiple print jobs a printjob with subcomponents if necessary, for example one for the E-mailmessage itself and one for each attachment to the E-mail. Theinformation associated with each print job or each print jobsubcomponent is passed to the rendering and conversion engine 1514,which renders and prints (S518) each job or subcomponent on the printer1816. In this example, the printed E-mail message may also serve as acover page or print job separator. However, a distinct cover page orseparator page, including addressing, subject and attachment informationfrom the printed E-mail may also be printed for a print E-mailoperation, for example when the printed E-mail has a different formatthan preferred cover or separator pages or perhaps where an E-mail isrelatively long, spanning several pages. When the printing operation iscompleted, the E-mail processor may then create a status E-mail messagewith the result of the operation and send the E-mail message back to themobile device 1802. An error message may also be prepared and returnedto the mobile device 1802 if an error occurred during processing of aprint job.

An E-mail to be printed on the printer 1816 may be composed on themobile device 1802 by a user, or may instead be and E-mail that wasreceived by the device. Where the device operates in conjunction with aredirection program operating at a host system such as 1808, the E-mailmay have been redirected to the mobile device 1802 from the host system1808. Regardless of the origin of the E-mail message to be printed, theE-mail and any attachments may be sent to and printed on the printer1816 as described above. In a device with a menu-driven user interfacefor example, an E-mail function menu may include a “Print” function inaddition to such traditional E-mail functions as “Send”, “Save”,“Forward” and the like. Upon selection of the “print” function andeither selection of a previously configured printer or service orconfiguration of a new printer or service, an E-mail and any associatedattachments on the device may be forwarded to and printed on a printerwith minimal time and effort on the part of the device user. It is alsocontemplated that a user of the mobile device 1802 may select one ormore particular E-mail message attachments to be printed. For example,if an E-mail message has more than one attachment, a user may wish toprint only one attachment with the E-mail. A user may also wish to printonly an attachment, without the E-mail message. In either of thesecases, a communication signal, such as an E-mail message for example,sent to the printer 1816 may include an indication or identifiers ofexactly what should be printed. The gateway 1814 or the printer 1816would then process the communication signal accordingly.

E-mail message attachments may also be forwarded to an informationprocessor by the host system 1808. In this case, a signal may be sentfrom the mobile device 1802 to the host system 1808, in response towhich the host system 1808 sends the attachment to the informationprocessor, such as the printer 1816.

Those skilled in the art will appreciate that a mobile communicationdevice and a printer are preferably enabled for different types ofinteraction. FIG. 19 shows a flow diagram of mobile device operationsassociated with a printing process incorporating multiple printingfunctions. When a print process is invoked on a mobile device at stepS1902, a check is performed at step S1904 to determined whether or not aprinter or service has been selected and identified, i.e. whether or notthe device has all the service information necessary to printinformation on a selected printer.

If any information, such as the unique identifier for the printer orservice, an address for the printer or service or any further serviceinformation required for a mobile device-controlled printing operationhas not yet been obtained by the mobile device, then the printer orservice identifier may first be captured, at step S1906, via one of theinterfaces described above. If the mobile device requires still furtherinformation as determined at step S1908, where the printer or serviceidentifier is not a routing address for example, the mobile device thenqueries the directory (S1910) to obtain the required information.

If the mobile device has obtained all service information required tocarry out the print operation, either before the print process begins orthrough steps S1906, S1908 and S1910, print processing continues at stepS1912. The mobile device determines if the information to be printed isresident on the mobile device, and if so, a communication signalincluding the information is sent to the printer (S1914) through anactive interface or an IP, URL or E-mail address, as shown in FIG. 16and described above. If the print operation is a print by referenceoperation however (S1916), then a communication signal includingreference information to be used by the printer gateway to retrieve thecontent to be printed is sent to the printer (S1918), as described abovein conjunction with FIG. 17. A print E-mail operation (S1920) proceedssubstantially as described above with reference to FIG. 18, when theE-mail to be printed is forwarded to the printer at step S1922. Asdescribed above, an E-mail or attachment may be forwarded to a printeror other information processor by a host system in response to acommunication signal sent to the host system from a mobile device. Theprinting process then ends at step S1924.

Although not explicitly shown in FIG. 19, when information to be printedis sent to the printer or service, the device may then await a responseindicating the status or successful completion of a print operation. Ifno response is received within a predetermined time or the responseinstead indicates that the printing process could not be completed, thenerror processing such as a printing retry operation, possibly using adifferent information transfer mechanism, a different service or adifferent printer for example, may be executed.

Printer operations in response to transmissions from a mobile deviceshould be apparent from the foregoing description. If the information tobe printed is in a message or signal received by the printer, then theinformation is rendered, converted and printed. For a print by referencecommand, the information to be printed is first retrieved and thenrendered, converted and printed.

Information processing control has been described in detail above in thecontext of an illustrative example of a printer. Those skilled in theart will appreciate that the operation of other information processorswill be similar to printer operations, although the actual informationprocessing operations may be different for other types of informationprocessors. For example, a display device will process and renderinformation in a format suitable for display on a screen or other outputinterface. An information processor may also be a fax machine whichwould convert information received from a mobile communication deviceinto a fax-compatible format and send a fax to a destination specifiedby the device.

Other types of information processors will preferably be configured toperform control operations and provide some sort of return informationto a device. For example, a device may receive E-mail attachments orfiles that it may be unable to process on its own. One or moreinformation processors may be provided with appropriate rendering andconversion engines to effectively translate such attachments or filesinto formats that can be processed by the device. The translation resultwould then preferably be returned to the device.

Information processors may also be implemented to provide for remotecontrol functions using a mobile communication device. A control filemay be prepared at or received on a mobile communication device and thenforwarded to an information processor which interfaces with a controlledsystem. If the control file is sent to the information processor as anE-mail attachment for example, then an E-mail processor in theinformation processor preferably separates the attachment from the emailmessage. If necessary, the control file may be compiled or otherwiseconverted into an appropriate preferably executable format if necessaryand executed by the information processor. The operation of thecontrolled system may thereby be started, stopped or otherwise changedin accordance with instructions in the executable control file. Such aninformation processor may then return a confirmation message to thedevice to inform the device user of the status of the control operation.Similarly, new control points or operating parameters may be forwardedto such an information processor and suitably rendered and convertedinto a control system input format if necessary. Other such configuringand provisioning of remote equipment may also be implemented inconjunction with information processors.

Menus or function lists for a device with menu-driven user interfacewould preferably be expanded to include additional supported functionsassociated with information processors. As those skilled in the art willappreciate, different devices may be differently enabled and thus mayhave different menus. When information processors or services areconfigured on a device, by storing the required information for aprocessor in a data store on the device, then submenus for each functionare preferably automatically expanded to include the configuredprocessors and services, such that the initial steps of identifiercapture and possibly directory querying can be avoided.

Having described in detail several preferred embodiments of the presentinvention, including preferred methods of operation, it is to beunderstood that this operation could be carried out with differentelements and steps. These preferred embodiments are presented only byway of example and are not meant to limit the scope of the presentinvention.

1. A method of processing information with an information processorusing a mobile communication device, comprising the steps of: obtainingat the mobile communication device, a unique identifier associated withthe information processor; receiving one or more messages at the mobilecommunication device; querying a service information provider using theunique identifier to obtain service information, the service informationincluding at least one service address associated with a serviceprovided by the information processor; and sending a communicationsignal that includes the one or more messages from the mobilecommunication device to the information processor using the at least oneservice address obtained from the service information provider, enablingthe information processor to perform an information processing operationin response to the communication signal.
 2. The method of claim 1,wherein the unique identifier is a network address of the informationprocessor.
 3. The method of claim 2, wherein the service informationprovider includes one or more service addresses linked to the networkaddress of the information processor.
 4. The method of claim 1, whereinthe step of obtaining a unique identifier is performed using a wirelesscommunication exchange between the mobile communication device and theinformation processor.
 5. The method of claim 4, wherein the wirelesscommunication exchange is a short-range RF communication exchange. 6.The method of claim 4, wherein the wireless communication exchange is aninfrared communication exchange.
 7. The method of claim 1, wherein theservice information provider directory associates a plurality ofinformation processors by location.
 8. The method of claim 1, whereinthe service information provider directory associates a plurality ofinformation processors by service type.
 9. The method of claim 1,wherein the querying step comprises the step of transmitting a queryfrom the mobile communication device to the service information providerdirectory via a wide area network.
 10. The method of claim 11, whereinthe wide area network is the Internet.
 11. The method of claim 1,wherein the communication signal includes information to be processed bythe information processor.
 12. The method of claim 11, wherein theinformation to be processed comprises an electronic mail message. 13.The method of claim 12, wherein the information to be processed furthercomprises an attachment.
 14. The method of claim 1, wherein thecommunication signal comprises a processing command to control theinformation processing operation.
 15. The method of claim 14, whereinthe communication signal further comprises information to be processedby the information processor.
 16. The method of claim 15, wherein: thecommunication signal further comprises a reference locator forinformation to be processed; and the step of performing a processingoperation comprises the step of retrieving the information to beprocessed using the reference locator.
 17. The method of claim 1,wherein: the at least one service address is a network addressassociated with a communication network; the mobile communication deviceis configured to send information to and receive information from awireless communication network; and the step of sending a communicationsignal comprises the step of sending the communication signal to theinformation processor via the wireless communication network and thecommunication network.
 18. The method of claim 17, wherein: thecommunication network is the Internet; and the at least one serviceaddress is an IP address or a Uniform Resource Locator (URL).
 19. Themethod of claim 17, wherein the service information provider is coupledto the communication network.
 20. The method of claim 1, wherein the atleast one service address is an electronic mail address.
 21. The methodof claim 1, wherein the information processing operation comprises aprinting operation.
 22. The method of claim 1, wherein the informationprocessing operation comprises a translation operation.
 23. The methodof claim 22, wherein: the translation operation translates informationinto a format that can be processed by the mobile communication device;and the method further comprises the step of sending translatedinformation from the information processor to the mobile communicationdevice.